diff options
| author | Christoph Hellwig <hch@lst.de> | 2024-03-04 17:04:48 +0300 |
|---|---|---|
| committer | Keith Busch <kbusch@kernel.org> | 2024-03-04 19:24:55 +0300 |
| commit | f404dd928b6667b383e684f2bd8cce507e031481 (patch) | |
| tree | 29f84ec97c89ad34476296dc70392d0563e2175b /tools/perf/scripts/python/stackcollapse.py | |
| parent | 1b2f5d5d288080ea10b4e2ed595c0dfb11557c17 (diff) | |
| download | linux-f404dd928b6667b383e684f2bd8cce507e031481.tar.xz | |
nvme: move max_integrity_segments handling out of nvme_init_integrity
max_integrity_segments is just a hardware limit and doesn't need to be
in nvme_init_integrity with the PI setup.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Max Gurtovoy <mgurtovoy@nvidia.com>
Signed-off-by: Keith Busch <kbusch@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions