From: Keith Busch <kbusch@kernel.org>
To: Qasim Ijaz <qasdev00@gmail.com>
Cc: james.smart@broadcom.com, axboe@kernel.dk, hch@lst.de,
sagi@grimberg.me, linux-nvme@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND] nvme-fc: Utilise min3() to simplify queue count calculation
Date: Mon, 3 Mar 2025 11:47:48 -0700 [thread overview]
Message-ID: <Z8X5VJgQ7yPfVTdd@kbusch-mbp> (raw)
In-Reply-To: <20250213221622.81457-1-qasdev00@gmail.com>
On Thu, Feb 13, 2025 at 10:16:22PM +0000, Qasim Ijaz wrote:
> Refactor nvme_fc_create_io_queues() and nvme_fc_recreate_io_queues() to
> use the min3() macro to find the minimum between 3 values instead of
> multiple min()'s. This shortens the code and makes it easier to read.
Thanks, applied to nvem-6.15.
prev parent reply other threads:[~2025-03-03 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 22:16 [PATCH RESEND] nvme-fc: Utilise min3() to simplify queue count calculation Qasim Ijaz
2025-03-03 18:47 ` Keith Busch [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=Z8X5VJgQ7yPfVTdd@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=james.smart@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=qasdev00@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