projects / linux-2.6-block.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: 9566b89) | patch
nvdimm/btt: always set max_integrity_segments
authorChristoph Hellwig <hch@lst.de>
Wed, 6 Mar 2024 14:27:38 +0000 (07:27 -0700)
committerIra Weiny <ira.weiny@intel.com>
Thu, 25 Apr 2024 19:37:12 +0000 (12:37 -0700)
commit1e97469678a0987174d8bec0d955b67e0048ac84
tree3ae17c63ee7f3ad07553e49b4095d0b0c346bb6dtree | snapshot
parent9566b89295196996bce57bf307bc634cb0713ceccommit | diff
nvdimm/btt: always set max_integrity_segments

max_integrity_segments is just a hardware/driver limit and can be safely
set even when integrity data is not supported.  Set it in the initial
queue_limits passed to blk_alloc_disk to simplify the driver.

Signed-off-by: Christoph Hellwig <hch@lst.de>
Link: https://lore.kernel.org/r/20240306142739.237234-3-hch@lst.de
Signed-off-by: Ira Weiny <ira.weiny@intel.com>
drivers/nvdimm/btt.c diff | blob | blame | history
Linux 6.x block layer and io_uring tree(s)