From: Christoph Hellwig <hch@lst.de>
To: Irvin Cote <irvincoteg@gmail.com>
Cc: hch@lst.de, kbusch@kernel.org, axboe@kernel.dk, sagi@grimberg.me,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH 1/1] nvme-core : remove redundant check from nvme_init_ns_head
Date: Sat, 20 May 2023 06:39:02 +0200 [thread overview]
Message-ID: <20230520043902.GG31780@lst.de> (raw)
In-Reply-To: <20230517220915.7244-1-irvincoteg@gmail.com>
On Wed, May 17, 2023 at 07:09:15PM -0300, Irvin Cote wrote:
> nvme_find_ns_head already checks that the list of namescpaces
> in an already existing namespace head is not empty
>
> Signed-off-by: Irvin Cote <irvincoteg@gmail.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2023-05-20 4:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 22:09 [PATCH 1/1] nvme-core : remove redundant check from nvme_init_ns_head Irvin Cote
2023-05-18 9:06 ` Sagi Grimberg
2023-05-19 2:29 ` Keith Busch
2023-05-19 3:31 ` irvin cote
2023-05-20 4:39 ` Christoph Hellwig
2023-05-20 4:39 ` 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=20230520043902.GG31780@lst.de \
--to=hch@lst.de \
--cc=axboe@kernel.dk \
--cc=irvincoteg@gmail.com \
--cc=kbusch@kernel.org \
--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