Cleanups in extent_io callbacks
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest4 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | btrfs: let writepage_end_io_hook return voidfs/ fs/ fs/ | +6 | 1 reply | |
| 2/4 | btrfs: document existence of extent_io ops callbacksfs/ fs/ fs/ | +26 | 0 replies | |
| 3/4 | btrfs: drop checks for mandatory extent_io_ops callbacksfs/ | +3 | 0 replies | |
| 4/4 | btrfs: add dummy callback for readpage_io_failed and drop checksfs/ fs/ fs/ +1 more | +10 | 1 reply |
Reviews trailers per patch
1 of 4 patches has a Reviewed-by or Acked-by.
| Patch | Liu Bo |
|---|---|
| 1/4 | R-b |
| 2/4 | |
| 3/4 | |
| 4/4 |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/4] Cleanups in extent_io callbacks
Some of the checks for extent_io callbacks can be safely dropped as they're always defined, plus some dummy callback additions so more checks can be dropped. There's more potential for the same cleanup in other callbacks but this would need more evaluation wheather dummy callbacks vs existence checks are really worth it.
David Sterba (4):
btrfs: let writepage_end_io_hook return void
btrfs: document existence of extent_io ops callbacks
btrfs: drop checks for mandatory extent_io_ops callbacks
btrfs: add dummy callback for readpage_io_failed and drop checks
fs/btrfs/disk-io.c | 7 +++++-- fs/btrfs/extent_io.c | 18 +++++++----------- fs/btrfs/extent_io.h | 25 +++++++++++++++++-------- fs/btrfs/inode.c | 20 ++++++++++++++------ 4 files changed, 43 insertions(+), 27 deletions(-)