From: "Toralf Förster" <toralf.foerster@gmx.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: FAT_DEFAULT_CODEPAGE and FAT_DEFAULT_IOCHARSET should auto-select NLS_CODEPAGE_437 and NLS_ISO8859_1 respectively
Date: Sat, 5 Jun 2021 10:00:19 +0200 [thread overview]
Message-ID: <6b15c8a9-ff00-5a9b-57fb-974028ec4de6@gmx.de> (raw)
I managed to boot a kernel (with UEFI boot) which wasn't able to mount
its VFAT boot partition afterwards due to unsetting those config options
by accident (== stupidity).
IMO the 2 former ones should select and pin their corresponding
partners, or?
--
Toralf
reply other threads:[~2021-06-05 8:00 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=6b15c8a9-ff00-5a9b-57fb-974028ec4de6@gmx.de \
--to=toralf.foerster@gmx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®