From: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Jan Kara <jack@suse.cz>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-ntfs-dev@lists.sourceforge.net, linux-cifs@vger.kernel.org,
Alexander Viro <viro@zeniv.linux.org.uk>,
Luis de Bethencourt <luisbg@kernel.org>,
Salah Triki <salah.triki@gmail.com>,
Steve French <sfrench@samba.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
David Sterba <dsterba@suse.com>,
Dave Kleikamp <shaggy@kernel.org>,
Anton Altaparmakov <anton@tuxera.com>, Jan Kara <jack@suse.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Eric Sandeen <sandeen@redhat.com>,
Namjae Jeon <linkinjeon@gmail.com>, Pavel Machek <pavel@ucw.cz>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: Unification of filesystem encoding options
Date: Wed, 08 Jan 2020 16:00:17 +0900 [thread overview]
Message-ID: <87y2uiigam.fsf@mail.parknet.co.jp> (raw)
In-Reply-To: <20200107173842.ciskn4ahuhiklycm@pali> ("Pali Rohár"'s message of "Tue, 7 Jan 2020 18:38:42 +0100")
Pali Rohár <pali.rohar@gmail.com> writes:
>> > 3) Add support for iocharset= and codepage= options for msdos
>> > filesystem. It shares lot of pars of code with vfat driver.
>>
>> I guess this is for msdos filesystem maintainers to decide.
>
> Yes!
Of course, it's ok to add though. If someone really wants to use, and
someone works for it...
Thanks.
--
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
prev parent reply other threads:[~2020-01-08 7:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-02 21:18 Unification of filesystem encoding options Pali Rohár
2020-01-07 13:32 ` Jan Kara
2020-01-07 17:38 ` Pali Rohár
2020-01-07 20:03 ` Theodore Y. Ts'o
2020-01-07 20:37 ` Pali Rohár
2020-01-08 7:13 ` OGAWA Hirofumi
2020-01-08 7:00 ` OGAWA Hirofumi [this message]
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=87y2uiigam.fsf@mail.parknet.co.jp \
--to=hirofumi@mail.parknet.co.jp \
--cc=anton@tuxera.com \
--cc=dsterba@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linkinjeon@gmail.com \
--cc=linux-cifs@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-ntfs-dev@lists.sourceforge.net \
--cc=luisbg@kernel.org \
--cc=pali.rohar@gmail.com \
--cc=pavel@ucw.cz \
--cc=salah.triki@gmail.com \
--cc=sandeen@redhat.com \
--cc=sfrench@samba.org \
--cc=shaggy@kernel.org \
--cc=tglx@linutronix.de \
--cc=tytso@mit.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 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.