Activity / Patch series
nvme: set max_hw_sectors unconditionally
Christoph Hellwig asahi linux-nvme 1 version Mar 4, 2024 In review
Get series with b4
Patches in v1 No applies recorded yet
Reviews trailers per patch
8 of 16 patches have a Reviewed-by or Acked-by.
Patch Max Gurtovoy Damien Le Moal John Garry
1/16 nvme: set max_hw_sectors unconditionally R-b R-b
2/16 nvme: move NVME_QUIRK_DEALLOCATE_ZEROES out of nvme_config_discard R-b
3/16 nvme: remove nvme_revalidate_zones R-b
4/16 nvme: move max_integrity_segments handling out of nvme_init_integrity R-b
5/16 nvme: cleanup the nvme_init_integrity calling conventions R-b
6/16 nvme: move blk_integrity_unregister into nvme_init_integrity R-b
7/16 nvme: don't use nvme_update_disk_info for the multipath disk
8/16 nvme: move a few things out of nvme_update_disk_info
9/16 nvme: move setting the write cache flags out of nvme_set_queue_limits R-b
10/16 nvme: move common logic into nvme_update_ns_info
11/16 nvme: split out a nvme_identify_ns_nvm helper R-b
12/16 nvme: don't query identify data in configure_metadata
13/16 nvme: cleanup nvme_configure_metadata
14/16 nvme: use the atomic queue limits update API
15/16 nvme-multipath: pass queue_limits to blk_alloc_disk
16/16 nvme-multipath: use atomic queue limits API for stacking limits
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 3 reviewers.
Read the v1 thread → Copy b4 command