From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@kernel.org>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@meta.com>,
linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: [RESEND PATCHv3 0/2] nvme effects handling updates
Date: Wed, 1 Feb 2023 16:10:43 +0100 [thread overview]
Message-ID: <20230201151043.GA6876@lst.de> (raw)
In-Reply-To: <Y9qAjNXsa1swaSb2@kbusch-mbp.dhcp.thefacebook.com>
On Wed, Feb 01, 2023 at 08:09:00AM -0700, Keith Busch wrote:
> On Wed, Feb 01, 2023 at 02:20:44PM +0100, Christoph Hellwig wrote:
> > Thanks,
> >
> > applied to nvme-6.2.
>
> Totally fine by me to put this in 6.2, though I assumed this was 6.3 material.
> The Security Receive behavior this series addresses is a little annoying, but
> not urgent.
I'll move it to 6.3.
prev parent reply other threads:[~2023-02-01 15:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 16:56 [RESEND PATCHv3 0/2] nvme effects handling updates Keith Busch
2023-01-27 16:56 ` [RESEND PATCHv3 1/2] nvme: always initialize known command effects Keith Busch
2023-01-31 9:41 ` Kanchan Joshi
2023-01-27 16:56 ` [RESEND PATCHv3 2/2] nvme: mask CSE effects for security receive Keith Busch
2023-01-31 21:40 ` [RESEND PATCHv3 0/2] nvme effects handling updates Chaitanya Kulkarni
2023-02-01 13:20 ` Christoph Hellwig
2023-02-01 15:09 ` Keith Busch
2023-02-01 15:10 ` Christoph Hellwig [this message]
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=20230201151043.GA6876@lst.de \
--to=hch@lst.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.