public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pekka Enberg <penberg@cs.helsinki.fi>
To: Joe Perches <joe@perches.com>, Ingo Molnar <mingo@elte.hu>,
	Vegard Nossum <vegard.nossum@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	x86@kernel.org, Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC/PATCH] x86: Use KERN_DEFAULT log-level in __show_regs()
Date: Tue, 29 Dec 2009 09:47:14 +0200	[thread overview]
Message-ID: <4B39B402.2040708@cs.helsinki.fi> (raw)
In-Reply-To: <1262072421.1888.57.camel@Joe-Laptop.home>

Hi Joe,

[ I'm restoring CC, dunno if I broke accidentally. ]

Joe Perches kirjoitti:
> On Tue, 2009-12-29 at 09:08 +0200, Pekka Enberg wrote:
>> Joe Perches kirjoitti:
>>> What is the reason to convert KERN_INFO to KERN_DEFAULT here?
>> To be consistent with rest of __show_regs() log-levels.
> 
> What log level is DEFAULT?
> 
> It's default 4 or WARNING, but I'd guess you had to
> look to find it.
> 
> Does anyone override it?
> 
> Why not simply specify KERN_WARNING for all of them?

For the reasons outlined here:

> from:
> $ git log -1 e28d713704117bca0820c732210df6075b09f13b
> This adds a KERN_DEFAULT loglevel marker, for when you cannot decide
> which loglevel you want, and just want to keep an existing printk
> with the default loglevel.

The whole point of the patch is to unify 32-bit and 64-bit wrt 
log-levels. The 32-bit version _is_ using KERN_DEFAULT implicitly and 
KERN_INFO is arguably wrong which is why I decided to go with the 
former. That way I don't need to go and audit all the callers of 
__show_regs() to see if KERN_WARN or some other level makes sense for them.

			Pekka

      parent reply	other threads:[~2009-12-29  7:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-28  8:26 [RFC/PATCH] x86: Use KERN_DEFAULT log-level in __show_regs() Pekka Enberg
2009-12-28 10:07 ` [tip:x86/urgent] " tip-bot for Pekka Enberg
2009-12-28 19:47 ` [RFC/PATCH] " Joe Perches
2009-12-29  7:08   ` Pekka Enberg
     [not found]     ` <1262072421.1888.57.camel@Joe-Laptop.home>
2009-12-29  7:47       ` Pekka Enberg [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=4B39B402.2040708@cs.helsinki.fi \
    --to=penberg@cs.helsinki.fi \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=vegard.nossum@gmail.com \
    --cc=x86@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