From: Xianting Tian <xianting_tian@126.com>
To: axboe@kernel.dk
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] block: Fix the typo in comment of function deadline_latter_request
Date: Wed, 13 Nov 2019 10:21:19 -0500 [thread overview]
Message-ID: <1573658479-13094-1-git-send-email-xianting_tian@126.com> (raw)
Fix the typo "`" to "'"
Signed-off-by: Xianting Tian <xianting_tian@126.com>
---
block/mq-deadline.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/block/mq-deadline.c b/block/mq-deadline.c
index b490f47..6047192 100644
--- a/block/mq-deadline.c
+++ b/block/mq-deadline.c
@@ -71,7 +71,7 @@ struct deadline_data {
}
/*
- * get the request after `rq' in sector-sorted order
+ * get the request after 'rq' in sector-sorted order
*/
static inline struct request *
deadline_latter_request(struct request *rq)
--
1.8.3.1
next reply other threads:[~2019-11-13 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 15:21 Xianting Tian [this message]
2019-11-13 15:57 ` [PATCH] block: Fix the typo in comment of function deadline_latter_request Bart Van Assche
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=1573658479-13094-1-git-send-email-xianting_tian@126.com \
--to=xianting_tian@126.com \
--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).