From: ownia <o451686892@gmail.com>
To: viro@zeniv.linux.org.uk
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ownia <o451686892@gmail.com>
Subject: [PATCH] fs/read_write.c: remove extra space
Date: Wed, 9 Sep 2020 06:07:42 -0700 [thread overview]
Message-ID: <20200909130742.81895-1-o451686892@gmail.com> (raw)
Signed-off-by: ownia <o451686892@gmail.com>
---
fs/read_write.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/read_write.c b/fs/read_write.c
index 5db58b8c78d0..4cdbf45ced98 100644
--- a/fs/read_write.c
+++ b/fs/read_write.c
@@ -1497,7 +1497,7 @@ static ssize_t do_sendfile(int out_fd, int in_fd, loff_t *ppos,
if (retval < 0)
goto fput_in;
if (count > MAX_RW_COUNT)
- count = MAX_RW_COUNT;
+ count = MAX_RW_COUNT;
/*
* Get output file, and verify that it is ok..
--
2.25.1
reply other threads:[~2020-09-09 14:13 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=20200909130742.81895-1-o451686892@gmail.com \
--to=o451686892@gmail.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;
as well as URLs for NNTP newsgroup(s).