public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Joe Perches <joe@perches.com>
Cc: Peter Zijlstra <peterz@infradead.org>, San Mehat <san@google.com>,
	Arjan van de Ven <arjan@infradead.org>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: sched: restore sanity
Date: Sun, 20 Dec 2009 18:37:27 +0100	[thread overview]
Message-ID: <20091220173727.GA12897@elte.hu> (raw)
In-Reply-To: <1261329743.30458.179.camel@Joe-Laptop.home>


* Joe Perches <joe@perches.com> wrote:

> On Sun, 2009-12-20 at 16:19 +0100, Peter Zijlstra wrote:
> > On Sun, 2009-12-20 at 07:05 -0800, San Mehat wrote:
> > > >> Probably, but the rest is just as annoying, pr_* is crap.
> > > Oh? Out of curiosity whats wrong with it?
> > That's what should be asked of printk().
> 
> pr_<level> offers some things printk cannot:
> 
> o standardization, eliminates frequent missing KERN_ levels
>   and missing/typo/misspelled module prefixes  
> o visually shorter, fewer chars used, less 80 char wrapping
> o finer grained ability to eliminate unnecessary messages
>   for embedded systems
> o standardized mechanism to prefix messages with module/function
> o eventual code reduction via use of a singleton instead of
>   duplicated module/function names
> o eventual dynamic_debug styled control of prefix by
>   module/function

These are pretty marginal advantages - borderline not worth the resulting 
churn. But borderline good patch is still a good patch in my book so i applied 
it. Btw., i wish you mixed with real kernel code too instead of going down the 
Bunk path. That would reduce such friction substantially IMO - people would 
see that you are willing to do (and capable of doing) the harder stuff too.

Thanks,

	Ingo

  parent reply	other threads:[~2009-12-20 17:37 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-20 13:23 sched: restore sanity Peter Zijlstra
2009-12-20 14:27 ` Arjan van de Ven
2009-12-20 14:49 ` Ingo Molnar
2009-12-20 14:51   ` Peter Zijlstra
     [not found]     ` <236ccac0912200703g464912b1r421497ebf3b6ebc6@mail.gmail.com>
2009-12-20 15:05       ` San Mehat
2009-12-20 15:19         ` Peter Zijlstra
2009-12-20 15:28           ` Mike Galbraith
2009-12-20 15:36           ` San Mehat
2009-12-20 17:22           ` Joe Perches
2009-12-20 17:36             ` Peter Zijlstra
2009-12-20 17:50               ` Ingo Molnar
2009-12-20 17:57               ` Joe Perches
2009-12-20 17:37             ` Ingo Molnar [this message]
2009-12-20 18:17             ` Arjan van de Ven
2009-12-20 18:21               ` Joe Perches
2009-12-21  0:48                 ` Arjan van de Ven
2009-12-21  1:20                   ` Joe Perches
2009-12-22 10:11             ` Al Viro
2009-12-20 17:22   ` Joe Perches
2009-12-20 18:00 ` [tip:sched/urgent] sched: Restore printk sanity tip-bot for Peter Zijlstra
2009-12-20 20:36   ` Geert Uytterhoeven
2009-12-21 20:40   ` Valdis.Kletnieks
2009-12-25 13:26   ` Pavel Machek
2009-12-25 18:45     ` Ingo Molnar
2009-12-27  0:45       ` Valdis.Kletnieks
2009-12-27  5:56         ` Ingo Molnar
     [not found]     ` <1261756819.4937.216.camel@laptop>
2009-12-25 18:39       ` Joe Perches
2009-12-25 18:47       ` Pavel Machek
2009-12-20 18:06 ` tip-bot for Peter Zijlstra
2009-12-20 18:55   ` Joe Perches
2009-12-20 19:15     ` Ingo Molnar
2009-12-20 19:44       ` [PATCH] scripts/checkpatch.pl: Add WARN on printk format split on multiple lines Joe Perches
2009-12-20 20:10         ` Ingo Molnar
2009-12-20 22:12       ` [tip:sched/urgent] sched: Restore printk sanity tytso
2009-12-21  1:11         ` Joe Perches

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=20091220173727.GA12897@elte.hu \
    --to=mingo@elte.hu \
    --cc=arjan@infradead.org \
    --cc=joe@perches.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=san@google.com \
    /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