From: Al Viro <viro@zeniv.linux.org.uk>
To: Namjae Jeon <linkinjeon@kernel.org>
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org,
Namjae Jeon <namjae.jeon@samsung.com>
Subject: Re: [PATCH] exfat: add the dummy mount options to be backward compatible with staging/exfat
Date: Thu, 21 May 2020 18:32:01 +0100 [thread overview]
Message-ID: <20200521173201.GG23230@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200521122034.2254-1-namjae.jeon@samsung.com>
On Thu, May 21, 2020 at 09:20:34PM +0900, Namjae Jeon wrote:
> As Ubuntu and Fedora release new version used kernel version equal to or
> higher than v5.4, They started to support kernel exfat filesystem.
>
> Linus Torvalds reported mount error with new version of exfat on Fedora.
>
> exfat: Unknown parameter 'namecase'
>
> This is because there is a difference in mount option between old
> staging/exfat and new exfat.
> And utf8, debug, and codepage options as well as namecase have been
> removed from new exfat.
>
> This patch add the dummy mount options as deprecated option to be backward
> compatible with old one.
>
> Reported-by: Linus Torvalds <torvalds@linux-foundation.org>
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Namjae Jeon <namjae.jeon@samsung.com>
Do you want that to go via vfs.git #fixes, or would you rather have Linus
apply it straight to mainline?
next prev parent reply other threads:[~2020-05-21 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-21 12:20 [PATCH] exfat: add the dummy mount options to be backward compatible with staging/exfat Namjae Jeon
2020-05-21 17:32 ` Al Viro [this message]
2020-05-21 23:28 ` Namjae Jeon
2020-05-21 23:41 ` Linus Torvalds
[not found] <CGME20200521234105epcas1p14b910bcdc017938249a491a1b5207bb8@epcas1p1.samsung.com>
[not found] ` <004401d62fc9$4ba36620$e2ea3260$@samsung.com>
2020-05-21 23:44 ` Namjae Jeon
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=20200521173201.GG23230@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linkinjeon@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=torvalds@linux-foundation.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).