From: Randy Dunlap <rdunlap@infradead.org>
To: linux-kernel@vger.kernel.org
Cc: Randy Dunlap <rdunlap@infradead.org>,
Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org
Subject: [PATCH 7/7] block: blk-timeout: delete duplicated word
Date: Thu, 30 Jul 2020 18:42:33 -0700 [thread overview]
Message-ID: <20200731014233.6418-8-rdunlap@infradead.org> (raw)
In-Reply-To: <20200731014233.6418-1-rdunlap@infradead.org>
Drop the repeated word "request".
Change to the correct kernel-doc notation for function name separtor.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
---
block/blk-timeout.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-next-20200730.orig/block/blk-timeout.c
+++ linux-next-20200730/block/blk-timeout.c
@@ -68,7 +68,7 @@ ssize_t part_timeout_store(struct device
#endif /* CONFIG_FAIL_IO_TIMEOUT */
/**
- * blk_abort_request -- Request request recovery for the specified command
+ * blk_abort_request - Request recovery for the specified command
* @req: pointer to the request of interest
*
* This function requests that the block layer start recovery for the
next prev parent reply other threads:[~2020-07-31 1:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 1:42 [PATCH 0/7] block: delete or fix duplicated words Randy Dunlap
2020-07-31 1:42 ` [PATCH 1/7] block: bfq-iosched: fix duplicated word Randy Dunlap
2020-07-31 1:42 ` [PATCH 2/7] block: bio: delete duplicated words Randy Dunlap
2020-07-31 1:42 ` [PATCH 3/7] block: elevator: delete duplicated word and fix typos Randy Dunlap
2020-07-31 1:42 ` [PATCH 4/7] block: genhd: delete duplicated words Randy Dunlap
2020-07-31 1:42 ` [PATCH 5/7] block: blk-mq: delete duplicated word Randy Dunlap
2020-07-31 1:42 ` [PATCH 6/7] block: blk-mq-sched: " Randy Dunlap
2020-07-31 1:42 ` Randy Dunlap [this message]
2020-07-31 22:30 ` [PATCH 0/7] block: delete or fix duplicated words 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=20200731014233.6418-8-rdunlap@infradead.org \
--to=rdunlap@infradead.org \
--cc=axboe@kernel.dk \
--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).