From: Yangtao Li via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>
To: jaegeuk@kernel.org, chao@kernel.org
Cc: Yangtao Li <frank.li@vivo.com>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: [f2fs-dev] [PATCH] f2fs: fix typo
Date: Sat, 11 Mar 2023 01:20:48 +0800 [thread overview]
Message-ID: <20230310172048.27996-1-frank.li@vivo.com> (raw)
s/not compatible/is not compatible
Signed-off-by: Yangtao Li <frank.li@vivo.com>
---
fs/f2fs/super.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c
index 9c87d91df61b..4c22f1b1da09 100644
--- a/fs/f2fs/super.c
+++ b/fs/f2fs/super.c
@@ -1350,7 +1350,7 @@ static int parse_options(struct super_block *sb, char *options, bool is_remount)
}
if (f2fs_is_readonly(sbi) && test_opt(sbi, FLUSH_MERGE)) {
- f2fs_err(sbi, "FLUSH_MERGE not compatible with readonly mode");
+ f2fs_err(sbi, "FLUSH_MERGE is not compatible with readonly mode");
return -EINVAL;
}
@@ -2342,7 +2342,7 @@ static int f2fs_remount(struct super_block *sb, int *flags, char *data)
if ((*flags & SB_RDONLY) && test_opt(sbi, DISABLE_CHECKPOINT)) {
err = -EINVAL;
- f2fs_warn(sbi, "disabling checkpoint not compatible with read-only");
+ f2fs_warn(sbi, "disabling checkpoint is not compatible with read-only");
goto restore_opts;
}
--
2.35.1
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
next reply other threads:[~2023-03-10 17:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 17:20 Yangtao Li via Linux-f2fs-devel [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-19 3:26 [f2fs-dev] [PATCH] f2fs: fix typo Yangtao Li via Linux-f2fs-devel
[not found] <CGME20220919023155epcms2p3f7040c348b5351a731f98c3f9c3a6847@epcms2p3>
2022-09-19 2:31 ` Yonggil Song
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=20230310172048.27996-1-frank.li@vivo.com \
--to=linux-f2fs-devel@lists.sourceforge.net \
--cc=chao@kernel.org \
--cc=frank.li@vivo.com \
--cc=jaegeuk@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).