From: Jason Wang <wangborong@cdjrlc.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Jason Wang <wangborong@cdjrlc.com>
Subject: [PATCH] fs/pipe.c: Fix comment typo
Date: Thu, 11 Aug 2022 22:01:07 +0800 [thread overview]
Message-ID: <20220811140107.29595-1-wangborong@cdjrlc.com> (raw)
The double `do' is duplicated in the comment, remove one.
Signed-off-by: Jason Wang <wangborong@cdjrlc.com>
---
fs/pipe.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/pipe.c b/fs/pipe.c
index 74ae9fafd25a..f4a070b12519 100644
--- a/fs/pipe.c
+++ b/fs/pipe.c
@@ -579,7 +579,7 @@ pipe_write(struct kiocb *iocb, struct iov_iter *from)
__pipe_unlock(pipe);
/*
- * If we do do a wakeup event, we do a 'sync' wakeup, because we
+ * If we do a wakeup event, we do a 'sync' wakeup, because we
* want the reader to start processing things asap, rather than
* leave the data pending.
*
--
2.36.1
reply other threads:[~2022-08-11 14:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220811140107.29595-1-wangborong@cdjrlc.com \
--to=wangborong@cdjrlc.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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®