From: Randy Dunlap <rdunlap@infradead.org>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>, axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>
Subject: [PATCH] trace/events/block.h: drop kernel-doc for dropped function parameter
Date: Mon, 15 Jun 2020 12:22:53 -0700 [thread overview]
Message-ID: <d572a150-192a-bbce-4449-8de45bce1a9b@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Fix kernel-doc warning: the parameter was removed, so also remove
the kernel-doc notation for it.
../include/trace/events/block.h:278: warning: Excess function parameter 'error' description in 'trace_block_bio_complete'
Fixes: d24de76af836 ("block: remove the error argument to the block_bio_complete tracepoint")
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Jens Axboe <axboe@kernel.dk>
---
include/trace/events/block.h | 1 -
1 file changed, 1 deletion(-)
--- linux-next-20200615.orig/include/trace/events/block.h
+++ linux-next-20200615/include/trace/events/block.h
@@ -254,7 +254,6 @@ TRACE_EVENT(block_bio_bounce,
* block_bio_complete - completed all work on the block operation
* @q: queue holding the block operation
* @bio: block operation completed
- * @error: io error value
*
* This tracepoint indicates there is no further work to do on this
* block IO operation @bio.
next reply other threads:[~2020-06-15 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 19:22 Randy Dunlap [this message]
2020-06-15 22:52 ` [PATCH] trace/events/block.h: drop kernel-doc for dropped function parameter 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=d572a150-192a-bbce-4449-8de45bce1a9b@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).