From: Christoph Hellwig <hch@lst.de>
To: Pankaj Raghav <pankydev8@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>,
sagi@grimberg.me, kbusch@kernel.org, sungup.moon@samsung.com,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: allow duplicate NSIDs for the private namespaces
Date: Mon, 28 Mar 2022 08:21:08 +0200 [thread overview]
Message-ID: <20220328062108.GA29315@lst.de> (raw)
In-Reply-To: <20220328053441.v6kr7gza7nj2ldlj@quentin>
On Mon, Mar 28, 2022 at 07:34:41AM +0200, Pankaj Raghav wrote:
> Is it s/uniqueue/unique/ ?
Thanks, I've fixed this up.
prev parent reply other threads:[~2022-03-28 6:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-24 15:43 [PATCH] nvme: allow duplicate NSIDs for the private namespaces Christoph Hellwig
2022-03-24 17:01 ` Sagi Grimberg
2022-03-28 5:34 ` Pankaj Raghav
2022-03-28 6:01 ` Sungup Moon
2022-03-28 6:21 ` 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=20220328062108.GA29315@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=pankydev8@gmail.com \
--cc=sagi@grimberg.me \
--cc=sungup.moon@samsung.com \
/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.