From: Keith Busch <kbusch@kernel.org>
To: guzebing <guzebing1612@gmail.com>
Cc: axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
Guzebing <guzebing@bytedance.com>
Subject: Re: [PATCH v3] nvme: reduce firmware activation poll interval
Date: Wed, 15 Jul 2026 16:49:47 -0600 [thread overview]
Message-ID: <algOi6OByZV9an8p@kbusch-mbp> (raw)
In-Reply-To: <20260715114401.1084214-1-guzebing1612@gmail.com>
On Wed, Jul 15, 2026 at 07:44:01PM +0800, guzebing wrote:
> ---
> Changes in v3:
> - Add a common polling delay helper for nvme_fw_act_work() and
> nvme_wait_ready().
I guess I was expecting the common helper to be the CSTS check and sleep
loop rather than just the sleep. I know the fw_act loop also checks the
ctrl_config in addition to CSTS, but that's fine to put in a common
function too.
prev parent reply other threads:[~2026-07-15 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-15 11:44 [PATCH v3] nvme: reduce firmware activation poll interval guzebing
2026-07-15 22:49 ` 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=algOi6OByZV9an8p@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=guzebing1612@gmail.com \
--cc=guzebing@bytedance.com \
--cc=hch@lst.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox