public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: lkml <linux-kernel@vger.kernel.org>
Cc: x86-ml <x86@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>
Subject: Re: Cleanup console loglevels
Date: Fri, 16 May 2014 19:51:54 +0200	[thread overview]
Message-ID: <20140516175154.GA18834@pd.tnic> (raw)
In-Reply-To: <20140516174921.GA18778@pd.tnic>

On Fri, May 16, 2014 at 07:49:21PM +0200, Borislav Petkov wrote:
> Hi,
> 
> so I was staring at
> 
> 12544697f12e ("x86_64: be less annoying on boot, v2")
> 
> and how naked numbers mean sh*t and how I have to grep sources to find
> out what this 10 thing means. So how about the following cleanup? We can
> do it this way, we can do accessors and stuff, whatever. But the naked
> numbers are plain misleading.
> 
> So how about it? I'm asking whether it makes sense first before I go
> and replace all tests of console_loglevel with naked numbers around the
> tree.
> 
> Thanks.
> 
> ---
> diff --git a/arch/x86/kernel/head64.c b/arch/x86/kernel/head64.c
> index 068054f4bf20..0029d974e431 100644
> --- a/arch/x86/kernel/head64.c
> +++ b/arch/x86/kernel/head64.c
> @@ -172,7 +172,7 @@ asmlinkage __visible void __init x86_64_start_kernel(char * real_mode_data)
>  	 */
>  	load_ucode_bsp();
>  
> -	if (console_loglevel == 10)
> +	if (console_loglevel >= CONSOLE_LOGLEVEL_QUIET)

That's CONSOLE_LOGLEVEL_DEBUG, of course.

See, misleading. :-P

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2014-05-16 17:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16 17:49 Cleanup console loglevels Borislav Petkov
2014-05-16 17:51 ` Borislav Petkov [this message]
2014-05-16 18:36   ` Randy Dunlap

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=20140516175154.GA18834@pd.tnic \
    --to=bp@alien8.de \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=torvalds@linux-foundation.org \
    --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