From: Jens Axboe <axboe@kernel.dk>
To: Bart Van Assche <bvanassche@acm.org>,
John Garry <john.g.garry@oracle.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Ming Lei <ming.lei@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] blk-mq: Fix more tag iteration function documentation
Date: Tue, 23 Sep 2025 12:27:20 -0600 [thread overview]
Message-ID: <49377ab3-0e5c-4767-8351-65a8d2340ad2@kernel.dk> (raw)
In-Reply-To: <3f32e7ee-e532-4d69-8848-43d44693e93a@acm.org>
On 9/23/25 9:59 AM, Bart Van Assche wrote:
> On 9/23/25 12:51 AM, John Garry wrote:
>> On 22/09/2025 21:13, Bart Van Assche wrote:
>>> diff --git a/block/blk-mq-tag.c b/block/blk-mq-tag.c
>>> index 0602ca7f1e37..271fa005c51e 100644
>>> --- a/block/blk-mq-tag.c
>>> +++ b/block/blk-mq-tag.c
>>> @@ -297,15 +297,15 @@ static bool bt_iter(struct sbitmap *bitmap, unsigned int bitnr, void *data)
>>> /**
>>> * bt_for_each - iterate over the requests associated with a hardware queue
>>> * @hctx: Hardware queue to examine.
>>> - * @q: Request queue to examine.
>>> + * @q: Request queue @hctx is associated with (@hctx->queue).
>>
>> eh, sometimes hctx is NULL, so it is odd to be saying that it is the q is associated with that (being NULL)
>
> Thanks for the feedback John.
>
> Jens, please let me know whether you want me to address this feedback in
> a follow-up patch or by posting a second version of this patch.
As per my applied email, it's already applied. And it's sitting a few
patches down at this point. I don't think there's a rush in fixing a
comment, so perhaps just do it next time you're touching that area
anyway.
--
Jens Axboe
prev parent reply other threads:[~2025-09-23 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-22 20:13 [PATCH] blk-mq: Fix more tag iteration function documentation Bart Van Assche
2025-09-23 6:23 ` Jens Axboe
2025-09-23 7:51 ` John Garry
2025-09-23 15:59 ` Bart Van Assche
2025-09-23 18:27 ` 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=49377ab3-0e5c-4767-8351-65a8d2340ad2@kernel.dk \
--to=axboe@kernel.dk \
--cc=bvanassche@acm.org \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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