[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20200406073543.rkxnsgegunlv3lkt@pali>
Date: Mon, 6 Apr 2020 09:35:43 +0200
From: Pali Rohár <pali@...nel.org>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Namjae Jeon <namjae.jeon@...sung.com>,
Al Viro <viro@...iv.linux.org.uk>,
Linux FS Devel <linux-fsdevel@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>,
Valdis Kletnieks <valdis.kletnieks@...edu>,
Christoph Hellwig <hch@....de>, sj1557.seo@...sung.com,
Arnd Bergmann <arnd@...db.de>, linkinjeon@...il.com
Subject: Re: [PATCH v14 11/14] exfat: add Kconfig and Makefile
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.
Powered by blists - more mailing lists