From: Jens Axboe <axboe@kernel.dk>
To: Randy Dunlap <rdunlap@infradead.org>, linux-kernel@vger.kernel.org
Cc: "André Almeida" <andrealmeid@collabora.com>,
"Ming Lei" <ming.lei@redhat.com>,
linux-block@vger.kernel.org
Subject: Re: [PATCH v2] block: blk-mq.c: fix @at_head kernel-doc warning
Date: Sun, 16 Aug 2020 16:50:58 -0700 [thread overview]
Message-ID: <174779d5-d698-0893-881a-3e371f2a1296@kernel.dk> (raw)
In-Reply-To: <20200816233934.1573-1-rdunlap@infradead.org>
On 8/16/20 4:39 PM, Randy Dunlap wrote:
> Fix a new kernel-doc warning in block/blk-mq.c:
>
> ../block/blk-mq.c:1844: warning: Function parameter or member 'at_head' not described in 'blk_mq_request_bypass_insert'
Replaced the previous one - and since I was doing that anyway, I removed
the 'new' from the commit message. Looks like it was from 5.6, so not
what I'd call new.
--
Jens Axboe
next prev parent reply other threads:[~2020-08-16 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 23:39 [PATCH v2] block: blk-mq.c: fix @at_head kernel-doc warning Randy Dunlap
2020-08-16 23:50 ` Jens Axboe [this message]
2020-08-16 23:56 ` Randy Dunlap
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=174779d5-d698-0893-881a-3e371f2a1296@kernel.dk \
--to=axboe@kernel.dk \
--cc=andrealmeid@collabora.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=rdunlap@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).