From: Randy Dunlap <rdunlap@infradead.org>
To: axboe <axboe@kernel.dk>, LKML <linux-kernel@vger.kernel.org>
Subject: [PATCH] block: fix blk-core.c kernel-doc warning
Date: Sun, 9 Aug 2015 18:37:33 -0700 [thread overview]
Message-ID: <55C8005D.6070704@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix kernel-doc warning in blk-core.c:
Warning(..//block/blk-core.c:1545): No description found for parameter 'same_queue_rq'
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
block/blk-core.c | 2 ++
1 file changed, 2 insertions(+)
--- lnx-42-rc6.orig/block/blk-core.c
+++ lnx-42-rc6/block/blk-core.c
@@ -1525,6 +1525,8 @@ bool bio_attempt_front_merge(struct requ
* @q: request_queue new bio is being queued at
* @bio: new bio being queued
* @request_count: out parameter for number of traversed plugged requests
+ * @same_queue_rq: pointer to &struct request that may be updated if same
+ * queue is found (optional, may be %NULL)
*
* Determine whether @bio being queued on @q can be merged with a request
* on %current's plugged list. Returns %true if merge was successful,
next reply other threads:[~2015-08-10 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-10 1:37 Randy Dunlap [this message]
2015-10-15 16:29 ` Jeff Moyer
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=55C8005D.6070704@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®