From: "Pali Rohár" <pali@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Namjae Jeon <namjae.jeon@samsung.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
Valdis Kletnieks <valdis.kletnieks@vt.edu>,
Christoph Hellwig <hch@lst.de>,
sj1557.seo@samsung.com, Arnd Bergmann <arnd@arndb.de>,
linkinjeon@gmail.com
Subject: Re: [PATCH v14 11/14] exfat: add Kconfig and Makefile
Date: Mon, 6 Apr 2020 09:35:43 +0200 [thread overview]
Message-ID: <20200406073543.rkxnsgegunlv3lkt@pali> (raw)
In-Reply-To: <CAMuHMdXdGDnvGYi1v1OhjCz=61moVRZQdZOtiKLG3m8q7vwkTg@mail.gmail.com>
On Monday 06 April 2020 09:27:01 Geert Uytterhoeven wrote:
> I tried to do it myself:
>
> Set this to the default input/output character set to use for
> converting between the encoding that is used for user visible
> filenames, and the UTF-16 character set that the exFAT filesystem
> uses. This can be overridden with the "iocharset" mount option for
> the exFAT filesystems.
>
> but then I got puzzled by the _3_ encodings that are part of it:
> 1. the default input/output character set to use for conversion,
> 2. encoding that is used for user visible filenames,
> 3. UTF-16 character set that the exFAT filesystem uses.
> I assume 1 == 2, but there may be more to it?
It is encoding between user visible filenames in VFS and UTF-16, so 1 == 2.
next prev parent reply other threads:[~2020-04-06 7:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200302062613epcas1p2969203b10bc3b7c41e0d4ffe9a08a3e9@epcas1p2.samsung.com>
2020-03-02 6:21 ` [PATCH v14 00/14] add the latest exfat driver Namjae Jeon
[not found] ` <CGME20200302062615epcas1p4fb5ead2437c08acc985a4bb0fe475d62@epcas1p4.samsung.com>
2020-03-02 6:21 ` [PATCH v14 01/14] exfat: add in-memory and on-disk structures and headers Namjae Jeon
[not found] ` <CGME20200302062616epcas1p3fa25e850df1874b50faed8e653860535@epcas1p3.samsung.com>
2020-03-02 6:21 ` [PATCH v14 02/14] exfat: add super block operations Namjae Jeon
[not found] ` <CGME20200302062617epcas1p1232f5fe2cb8860226a359e86a64079e8@epcas1p1.samsung.com>
2020-03-02 6:21 ` [PATCH v14 03/14] exfat: add inode operations Namjae Jeon
[not found] ` <CGME20200302062618epcas1p40ac59f8bb9c4102c532192923e38b465@epcas1p4.samsung.com>
2020-03-02 6:21 ` [PATCH v14 04/14] exfat: add directory operations Namjae Jeon
[not found] ` <CGME20200302062619epcas1p3baada4a058b582bc1a75ed9355320979@epcas1p3.samsung.com>
2020-03-02 6:21 ` [PATCH v14 05/14] exfat: add file operations Namjae Jeon
[not found] ` <CGME20200302062620epcas1p3ba4cc2c52d4e9e88d8a6cb08e9ef6995@epcas1p3.samsung.com>
2020-03-02 6:21 ` [PATCH v14 06/14] exfat: add fat entry operations Namjae Jeon
[not found] ` <CGME20200302062621epcas1p1be0044bf44ff08c90a3a8208fe3215e8@epcas1p1.samsung.com>
2020-03-02 6:21 ` [PATCH v14 07/14] exfat: add bitmap operations Namjae Jeon
[not found] ` <CGME20200302062622epcas1p47a6afcb4cc689858023076060b009ff8@epcas1p4.samsung.com>
2020-03-02 6:21 ` [PATCH v14 08/14] exfat: add exfat cache Namjae Jeon
[not found] ` <CGME20200302062623epcas1p11c5190e04bac06999674e4e41ac800d8@epcas1p1.samsung.com>
2020-03-02 6:21 ` [PATCH v14 09/14] exfat: add misc operations Namjae Jeon
[not found] ` <CGME20200302062624epcas1p2bf05cbbebc9197d1645ad78b1a369b3b@epcas1p2.samsung.com>
2020-03-02 6:21 ` [PATCH v14 10/14] exfat: add nls operations Namjae Jeon
[not found] ` <CGME20200302062625epcas1p200c53fabe17996e92257a409b7a9c857@epcas1p2.samsung.com>
2020-03-02 6:21 ` [PATCH v14 11/14] exfat: add Kconfig and Makefile Namjae Jeon
2020-04-06 7:27 ` Geert Uytterhoeven
2020-04-06 7:35 ` Pali Rohár [this message]
[not found] ` <CGME20200302062627epcas1p40f1ac87d14fca82d278beaded987f0fb@epcas1p4.samsung.com>
2020-03-02 6:21 ` [PATCH v14 12/14] MAINTAINERS: add exfat filesystem Namjae Jeon
[not found] ` <CGME20200302062628epcas1p159ad0d797c1d4334fbcaf84f39bfea40@epcas1p1.samsung.com>
2020-03-02 6:21 ` [PATCH v14 13/14] staging: exfat: make staging/exfat and fs/exfat mutually exclusive Namjae Jeon
[not found] ` <CGME20200302062629epcas1p46967161019cd142c17a9ee7d33ae9265@epcas1p4.samsung.com>
2020-03-02 6:21 ` [PATCH v14 14/14] exfat: update file system parameter handling Namjae Jeon
2020-03-05 15:53 ` [PATCH v14 00/14] add the latest exfat driver Christoph Hellwig
2020-03-05 16:12 ` Al Viro
2020-03-06 12:12 ` 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=20200406073543.rkxnsgegunlv3lkt@pali \
--to=pali@kernel.org \
--cc=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=linkinjeon@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=namjae.jeon@samsung.com \
--cc=sj1557.seo@samsung.com \
--cc=valdis.kletnieks@vt.edu \
--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).