From: Michal Marek <mmarek@suse.cz>
To: "Manolo Díaz" <diaz.manolo@gmail.com>
Cc: linux-kbuild@vger.kernel.org
Subject: Re: PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work
Date: Mon, 08 Apr 2013 12:50:13 +0200 [thread overview]
Message-ID: <5162A0E5.3050903@suse.cz> (raw)
In-Reply-To: <20130315234307.2f2846c8@merope>
On 15.3.2013 23:43, Manolo Díaz wrote:
> Hi,
>
> It seems that the kernel loglevel is set to 7 ignoring the
> CONFIG_DEFAULT_MESSAGE_LOGLEVEL option (set to 4 in my config file)
>
> The /proc/sys/kernel/printk output is
>
> 7 4 1 7
The default message loglevel (loglevel for messages with no explicitly
defined priority) is the second number. The first number is the console
loglevel.
Michal
next prev parent reply other threads:[~2013-04-08 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 22:43 PROBLEM: CONFIG_DEFAULT_MESSAGE_LOGLEVEL option seems not to work Manolo Díaz
2013-04-08 10:50 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-15 21:56 Manolo Díaz
2013-03-16 4:54 ` Randy Dunlap
2013-03-16 11:01 ` Manolo Díaz
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=5162A0E5.3050903@suse.cz \
--to=mmarek@suse.cz \
--cc=diaz.manolo@gmail.com \
--cc=linux-kbuild@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