From: Jens Axboe <axboe@kernel.dk>
To: Chaitanya Kulkarni <kch@nvidia.com>,
Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
Sagi Grimberg <sagi@grimberg.me>,
Mohamed Khalfella <mkhalfella@purestorage.com>
Cc: Casey Chen <cachen@purestorage.com>,
Yuanyuan Zhong <yzhong@purestorage.com>,
Hannes Reinecke <hare@suse.de>, Ming Lei <ming.lei@redhat.com>,
Waiman Long <llong@redhat.com>, Hillf Danton <hdanton@sina.com>,
linux-nvme@lists.infradead.org, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 0/1] block: Use RCU in blk_mq_[un]quiesce_tagset() instead of set->tag_list_lock
Date: Tue, 09 Dec 2025 10:34:04 -0700 [thread overview]
Message-ID: <176530164449.86086.1886657108099467825.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251205211738.1872244-1-mkhalfella@purestorage.com>
On Fri, 05 Dec 2025 13:17:01 -0800, Mohamed Khalfella wrote:
> Changes from v3:
> - Fixed typos in commit message.
> - Updated stacktrace in commit message with one taken from recent kernel.
> - Added Fixes: tag to commit message.
> - Deleted synchronize_rcu() (added in v3) and pre-existing
> INIT_LIST_HEAD(&q->tag_set_list) call in blk_mq_del_queue_tag_set().
> - Updated the commit message to mention why it is safe to delete
> INIT_LIST_HEAD(&q->tag_set_list) in blk_mq_del_queue_tag_set().
>
> [...]
Applied, thanks!
[1/1] block: Use RCU in blk_mq_[un]quiesce_tagset() instead of set->tag_list_lock
commit: 59e25ef2b413c72da6686d431e7759302cfccafa
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-12-09 17:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 21:17 Mohamed Khalfella
2025-12-05 21:17 ` [PATCH v4 1/1] " Mohamed Khalfella
2025-12-08 19:28 ` Bart Van Assche
2025-12-09 4:04 ` Ming Lei
2025-12-09 7:30 ` Hannes Reinecke
2025-12-09 17:00 ` Bart Van Assche
2025-12-09 17:49 ` Mohamed Khalfella
2025-12-09 17:34 ` Jens Axboe [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=176530164449.86086.1886657108099467825.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=cachen@purestorage.com \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=hdanton@sina.com \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=llong@redhat.com \
--cc=ming.lei@redhat.com \
--cc=mkhalfella@purestorage.com \
--cc=sagi@grimberg.me \
--cc=yzhong@purestorage.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®