diff options
author | 2024-03-06 07:27:38 -0700 | |
---|---|---|
committer | 2024-04-25 12:37:12 -0700 | |
commit | 1e97469678a0987174d8bec0d955b67e0048ac84 (patch) | |
tree | 3ae17c63ee7f3ad07553e49b4095d0b0c346bb6d /scripts/syscallnr.sh | |
parent | nvdimm: remove nd_integrity_init (diff) | |
download | linux-1e97469678a0987174d8bec0d955b67e0048ac84.tar.gz linux-1e97469678a0987174d8bec0d955b67e0048ac84.tar.bz2 linux-1e97469678a0987174d8bec0d955b67e0048ac84.zip |
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>
Diffstat (limited to 'scripts/syscallnr.sh')
0 files changed, 0 insertions, 0 deletions