From: Kamaljit Singh <kamaljit.singh@opensource.wdc.com>
To: Hannes Reinecke <hare@suse.de>
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
cassel@kernel.org, dlemoal@kernel.org, kamaljit.singh1@wdc.com
Subject: Re: [PATCH v2 2/2] nvme-core: do ioccsz/iorcsz validation only for I/O controllers
Date: Wed, 17 Sep 2025 14:43:28 -0700 [thread overview]
Message-ID: <aMsrgNycCQOCO9Sd@opensource.wdc.com> (raw)
In-Reply-To: <1077309c-2e91-4f0d-b8a6-69d3f9d60cac@suse.de>
On Mon, Sep 08, 2025 at 02:57:00PM +0200, Hannes Reinecke wrote:
> On 9/6/25 01:25, Kamaljit Singh wrote:
> > An administrative controller does not support I/O queues, hence it
> > should ignore existing checks for IOCCSZ/IORCSZ. Currently, these checks
> > only exclude a discovery controller but need to also exclude an
> > administrative controller.
> >
> > Signed-off-by: Kamaljit Singh <kamaljit.singh@opensource.wdc.com>
> > ---
> > drivers/nvme/host/core.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> Reviewed-by: Hannes Reinecke <hare@suse.de>
>
Please review and provide any feedback for both of these patches.
Thanks,
Kamaljit
next prev parent reply other threads:[~2025-09-17 21:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 23:25 [PATCH v2 0/2] Preclude IOCCSZ/IORCSZ validation for admin controller connect Kamaljit Singh
2025-09-05 23:25 ` [PATCH v2 1/2] nvme-core: add method to check for an I/O controller Kamaljit Singh
2025-09-08 12:56 ` Hannes Reinecke
2025-09-17 21:42 ` Kamaljit Singh
2025-09-05 23:25 ` [PATCH v2 2/2] nvme-core: do ioccsz/iorcsz validation only for I/O controllers Kamaljit Singh
2025-09-08 12:57 ` Hannes Reinecke
2025-09-17 21:43 ` Kamaljit Singh [this message]
2025-09-17 22:41 ` [PATCH v2 0/2] Preclude IOCCSZ/IORCSZ validation for admin controller connect 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=aMsrgNycCQOCO9Sd@opensource.wdc.com \
--to=kamaljit.singh@opensource.wdc.com \
--cc=axboe@kernel.dk \
--cc=cassel@kernel.org \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kamaljit.singh1@wdc.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.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 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.