)]}'
{
  "commit": "7fbabbb4ae2a7203861e4db363e3c861a4df260e",
  "tree": "4239ed2c4f7f0933e6d9f3a7fc0c86481a8c56a0",
  "parents": [
    "47ac09b91befbb6a235ab620c32af719f8208399",
    "4acaddf5d1e78814d26df3ff02d5e410d951ff32"
  ],
  "author": {
    "name": "Christian Brauner",
    "email": "brauner@kernel.org",
    "time": "Wed Aug 28 16:54:05 2024 +0200"
  },
  "committer": {
    "name": "Christian Brauner",
    "email": "brauner@kernel.org",
    "time": "Wed Aug 28 16:54:05 2024 +0200"
  },
  "message": "Merge patch series \"Subject: sort out the fallocate mode mess\"\n\nChristoph Hellwig \u003chch@lst.de\u003e says:\n\nI\u0027ve recently been looking at the XFS fallocate implementation and got\nupset about the messing parsing of the mode argument, which mixes modes\nand an optional flag in a really confusing way.\n\nThis series tries to clean this up by better defining what is the\noperation mode and what is an optional flag, so that both the core\ncode and file systems can use switch statements to switch on the mode.\n\n* patches from https://lore.kernel.org/r/20240827065123.1762168-1-hch@lst.de:\n  xfs: refactor xfs_file_fallocate\n  xfs: move the xfs_is_always_cow_inode check into xfs_alloc_file_space\n  xfs: call xfs_flush_unmap_range from xfs_free_file_space\n  fs: sort out the fallocate mode vs flag mess\n  ext4: remove tracing for FALLOC_FL_NO_HIDE_STALE\n  block: remove checks for FALLOC_FL_NO_HIDE_STALE\n\nLink: https://lore.kernel.org/r/20240827065123.1762168-1-hch@lst.de\nSigned-off-by: Christian Brauner \u003cbrauner@kernel.org\u003e\n",
  "tree_diff": []
}