From: Mihai Moldovan <ionic@ionic.de>
To: Jesper Juhl <jj@chaosbits.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Subject: Re: [PATCH] fix fat utf8 iocharset warning message
Date: Sun, 24 Jul 2011 20:19:12 +0200 [thread overview]
Message-ID: <4E2C6220.5070706@ionic.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1107241921350.5758@swampdragon.chaosbits.net>
[-- Attachment #1: Type: text/plain, Size: 393 bytes --]
* On 24.07.2011 07:22 PM, Jesper Juhl wrote:
> @@ -1190,7 +1190,7 @@ out:
> if (!strcmp(opts->iocharset, "utf8")) {
> fat_msg(sb, KERN_ERR, "utf8 is not a recommended IO charset"
> Is KERN_ERR really the right thing to use here?
> Sounds more like a warning to me..
I'm interested to see what Ogawa says, but I'd say KERN_WARNING would be
better here as well, yeah.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4369 bytes --]
next prev parent reply other threads:[~2011-07-24 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-24 13:37 [PATCH] fix fat utf8 iocharset warning message Mihai Moldovan
2011-07-24 17:22 ` Jesper Juhl
2011-07-24 18:19 ` Mihai Moldovan [this message]
2011-07-25 20:20 ` OGAWA Hirofumi
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=4E2C6220.5070706@ionic.de \
--to=ionic@ionic.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=jj@chaosbits.net \
--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