From: root <jeremy.cochoy@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, Manish Katiyar <mkatiyar@gmail.com>,
Jan Kara <jack@suse.cz>,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@lst.de>, Al Viro <viro@zeniv.linux.org.uk>,
Corentin Chary <corentin.chary@gmail.com>
Subject: [PATCH] fix ext2 parse_options printk
Date: Mon, 7 Dec 2009 15:01:00 +0100 [thread overview]
Message-ID: <1260194461-8937-1-git-send-email-jeremy.cochoy@gmail.com> (raw)
Hello,
I added KERN_* prexif in some log message. I choose KERN_NOTICE for message who looks something the user might be warned, because it isn't really a warning but it's something he should know.
I chose KERN_INFO for 2 elements which are what the user asked to be.
Tell me if there is any problem with my choices (or i make any mistake while sending you this patch) or anything else :)
Best regars,
next reply other threads:[~2009-12-07 13:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-07 14:01 root [this message]
2009-12-07 14:01 ` [PATCH] fix ext2 parse_options printk root
2009-12-08 10:00 ` Jan Kara
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=1260194461-8937-1-git-send-email-jeremy.cochoy@gmail.com \
--to=jeremy.cochoy@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=corentin.chary@gmail.com \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkatiyar@gmail.com \
--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).