From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: Chao Yu <chao.yu@linux.dev>,
linux-kernel@vger.kernel.org,
linux-f2fs-devel@lists.sourceforge.net
Subject: Re: [f2fs-dev] [PATCH] f2fs: fix wrong option name printed by parse_options()
Date: Tue, 24 Aug 2021 09:31:47 +0800 [thread overview]
Message-ID: <eadccf3a-057f-4d79-895d-140927167b69@kernel.org> (raw)
In-Reply-To: <20210824011948.15408-1-chao@kernel.org>
On 2021/8/24 9:19, Chao Yu wrote:
> It prints below kernel message during mounting w/ checkpoint=disable
> option:
>
> "F2FS-fs (pmem0): checkpoint=merge cannot be used with checkpoint=disable"
Oops, this message should have been removed by
"f2fs: rename checkpoint=merge mount option to checkpoint_merge"
I may used old f2fs module, please ignore this...
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <chao@kernel.org>
To: jaegeuk@kernel.org
Cc: linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, Chao Yu <chao.yu@linux.dev>
Subject: Re: [PATCH] f2fs: fix wrong option name printed by parse_options()
Date: Tue, 24 Aug 2021 09:31:47 +0800 [thread overview]
Message-ID: <eadccf3a-057f-4d79-895d-140927167b69@kernel.org> (raw)
In-Reply-To: <20210824011948.15408-1-chao@kernel.org>
On 2021/8/24 9:19, Chao Yu wrote:
> It prints below kernel message during mounting w/ checkpoint=disable
> option:
>
> "F2FS-fs (pmem0): checkpoint=merge cannot be used with checkpoint=disable"
Oops, this message should have been removed by
"f2fs: rename checkpoint=merge mount option to checkpoint_merge"
I may used old f2fs module, please ignore this...
next prev parent reply other threads:[~2021-08-24 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 1:19 [PATCH] f2fs: fix wrong option name printed by parse_options() Chao Yu
2021-08-24 1:19 ` [f2fs-dev] " Chao Yu
2021-08-24 1:31 ` Chao Yu [this message]
2021-08-24 1:31 ` Chao Yu
2021-08-24 17:26 ` [f2fs-dev] " Jaegeuk Kim
2021-08-24 17:26 ` Jaegeuk Kim
2021-08-24 23:35 ` Chao Yu
2021-08-24 23:35 ` [f2fs-dev] " Chao Yu
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=eadccf3a-057f-4d79-895d-140927167b69@kernel.org \
--to=chao@kernel.org \
--cc=chao.yu@linux.dev \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.