public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Kanchan Joshi <joshi.k@samsung.com>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
	Keith Busch <kbusch@kernel.org>
Subject: Re: [RESEND PATCHv3 1/2] nvme: always initialize known command effects
Date: Tue, 31 Jan 2023 15:11:34 +0530	[thread overview]
Message-ID: <20230131094134.GA17740@green5> (raw)
In-Reply-To: <20230127165620.3487918-2-kbusch@meta.com>

[-- Attachment #1: Type: text/plain, Size: 357 bytes --]

On Fri, Jan 27, 2023 at 08:56:19AM -0800, Keith Busch wrote:
>From: Keith Busch <kbusch@kernel.org>
>
>Instead of appending command effects flags per IO, set the known effects
>flags the driver needs to react to just once during initial setup.
>
>Signed-off-by: Keith Busch <kbusch@kernel.org>

Looks good.
Reviewed-by: Kanchan Joshi <joshi.k@samsung.com>


[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2023-01-31 10:07 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 [this message]
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

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=20230131094134.GA17740@green5 \
    --to=joshi.k@samsung.com \
    --cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox