From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>
Subject: Re: [PATCH] nvme: mask CSE effects for security receive
Date: Mon, 23 Jan 2023 17:41:18 +0100 [thread overview]
Message-ID: <20230123164118.GA8398@lst.de> (raw)
In-Reply-To: <20230120171731.652371-1-kbusch@meta.com>
As-is this only applies to nvme-6.3, is that intended?
next prev parent reply other threads:[~2023-01-23 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 17:17 [PATCH] nvme: mask CSE effects for security receive Keith Busch
2023-01-20 19:39 ` Jens Axboe
2023-01-23 9:03 ` Sagi Grimberg
2023-01-23 16:41 ` Christoph Hellwig [this message]
2023-01-23 16:43 ` Christoph Hellwig
2023-01-23 16:47 ` Keith Busch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230123164118.GA8398@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox