From: Christoph Hellwig <hch@lst.de>
To: Martin George <martinus.gpy@gmail.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, kbusch@kernel.org,
sagi@grimberg.me, Martin George <marting@netapp.com>
Subject: Re: [PATCH] nvme-core: use nvme_is_io_ctrl() for I/O controller check
Date: Mon, 22 Sep 2025 19:08:15 +0200 [thread overview]
Message-ID: <20250922170815.GB12527@lst.de> (raw)
In-Reply-To: <20250922120532.3754-1-marting@netapp.com>
On Mon, Sep 22, 2025 at 05:35:32PM +0530, Martin George wrote:
> Replace the current I/O controller check in
> nvme_init_non_mdts_limits() with the helper nvme_is_io_ctrl()
> function to maintain consistency with similar checks in other
> parts of the code and improve code readability.
>
> Signed-off-by: Martin George <marting@netapp.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2025-09-22 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 12:05 [PATCH] nvme-core: use nvme_is_io_ctrl() for I/O controller check Martin George
2025-09-22 17:08 ` Christoph Hellwig [this message]
2025-09-22 20:23 ` 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=20250922170815.GB12527@lst.de \
--to=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=marting@netapp.com \
--cc=martinus.gpy@gmail.com \
--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