linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "zhenwei.pi" <zhenwei.pi@youruncloud.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca
Cc: zhenwei.pi@youruncloud.com, linux-ext4@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH] ext4 : fix comments in ext4_swap_extents
Date: Sat, 24 Mar 2018 15:28:24 +0800	[thread overview]
Message-ID: <1521876504-18326-1-git-send-email-zhenwei.pi@youruncloud.com> (raw)

"mark_unwritten" in comment and "unwritten" in variable
argument lists is mismatch.

Signed-off-by: zhenwei.pi <zhenwei.pi@youruncloud.com>
---
 fs/ext4/extents.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 054416e..2fc4227 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -5751,7 +5751,7 @@ int ext4_insert_range(struct inode *inode, loff_t offset, loff_t len)
  * @lblk1:	Start block for first inode
  * @lblk2:	Start block for second inode
  * @count:	Number of blocks to swap
- * @mark_unwritten: Mark second inode's extents as unwritten after swap
+ * @unwritten: Mark second inode's extents as unwritten after swap
  * @erp:	Pointer to save error value
  *
  * This helper routine does exactly what is promise "swap extents". All other
-- 
2.7.4

             reply	other threads:[~2018-03-24  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-24  7:28 zhenwei.pi [this message]
2018-03-26  5:46 ` [PATCH] ext4 : fix comments in ext4_swap_extents Theodore Y. Ts'o
  -- strict thread matches above, loose matches on Subject: below --
2018-03-19  8:34 zhenwei.pi
2018-04-19 14:50 ` Jan Kara
2018-04-19 16:44   ` Theodore Y. Ts'o
2018-04-19 20:13     ` Jan Kara

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=1521876504-18326-1-git-send-email-zhenwei.pi@youruncloud.com \
    --to=zhenwei.pi@youruncloud.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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).