From: Jens Axboe <axboe@kernel.dk>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH] block: improve kerneldoc of blk_mq_add_to_batch()
Date: Wed, 12 Mar 2025 07:26:13 -0600 [thread overview]
Message-ID: <6f10a6df-e672-43f5-a82d-5e936fcdbba9@kernel.dk> (raw)
In-Reply-To: <20250312072712.1777580-1-shinichiro.kawasaki@wdc.com>
On 3/12/25 1:27 AM, Shin'ichiro Kawasaki wrote:
> Commit f00baf2eac78 ("block: change blk_mq_add_to_batch() third argument
> type to bool") added kerneldoc style comment of blk_mq_add_to_batch().
> However, it did not follow the kerneldoc format and was incomplete.
> Improve the comment to follow the format.
Thanks, I'll fold this in to the other patch.
--
Jens Axboe
next prev parent reply other threads:[~2025-03-12 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 7:27 [PATCH] block: improve kerneldoc of blk_mq_add_to_batch() Shin'ichiro Kawasaki
2025-03-12 7:43 ` Christoph Hellwig
2025-03-12 13:26 ` Jens Axboe [this message]
2025-03-12 14:27 ` Jens Axboe
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=6f10a6df-e672-43f5-a82d-5e936fcdbba9@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=linux-block@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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