diff options
| author | Hannes Reinecke <hare@suse.de> | 2022-12-08 08:49:20 +0100 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2023-02-01 14:21:58 +0100 |
| commit | 0686fb3cc535c4c1685553c56f4efe3eeee57b09 (patch) | |
| tree | 7e00b4217058e162aad338b4108186537e0595e2 /Kconfig | |
| parent | block: Remove mm.h from bvec.h (diff) | |
| download | linux-0686fb3cc535c4c1685553c56f4efe3eeee57b09.tar.xz linux-0686fb3cc535c4c1685553c56f4efe3eeee57b09.zip | |
nvme-fabrics: clarify AUTHREQ result handling
The NVMe 2.0 spec defines the ATR and ASCR bits in the AUTHREQ
connect response field to be mutually exclusive. So to clarify the
handling here switch the AUTHREQ handling to use the bit definitions
and check for both bits.
And while we're at it, add a message to the user that secure
concatenation is not supported (yet).
Suggested-by: Mark Lehrer <mark.lehrer@wdc.com>
Signed-off-by: Hannes Reinecke <hare@suse.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'Kconfig')
0 files changed, 0 insertions, 0 deletions