public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <guenter.roeck@ericsson.com>
To: Jean Delvare <khali@linux-fr.org>
Cc: Joe Perches <joe@perches.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [RFC PATCH] include/linux/kernel.h: Add config option for pr_fmt(fmt)
Date: Mon, 8 Nov 2010 08:55:26 -0800	[thread overview]
Message-ID: <20101108165526.GA20229@ericsson.com> (raw)
In-Reply-To: <20101108133342.7217866c@endymion.delvare>

On Mon, Nov 08, 2010 at 07:33:42AM -0500, Jean Delvare wrote:
> Hi Joe,
> 
> Sorry for the late answer.
> 
> On Fri, 29 Oct 2010 15:10:50 -0700, Joe Perches wrote:
> > On Thu, 2010-10-28 at 10:43 +0200, Jean Delvare wrote:
> > > Besides, linux-next is meant for integration testing. We already know
> > > that the change will integrate fine, in that it won't cause a build
> > > failure or runtime crash. We also know that, without the tree-wide
> > > cleanup of many driver, the change will cause duplicate prefixes in
> > > many messages.
> > > 
> > > There's little point in testing something we know will not be good
> > > enough. Better prepare all the driver patches, and test the whole thing
> > > when it's ready. I know it will be a very large and intrusive patchset,
> > > but this can certainly be done with Andrew's support.
> > 
> > I think you underestimate the time, effort and acceptance
> > levels by the various arches and maintainers required.
> > 
> > Also, it's not just drivers, it's arch, lib, and kernel.
> > (...)
> 
> I've had time to think about it all some more, and I have to admit that
> my counter-proposal doesn't really fly. Changing everything at once
> throughout the whole kernel tree is simply too difficult.
> 
> So I hate to admit it, but your initial proposal was certainly better,
> because it can be done one subsystem at a time. So I think we should
> forget about my objections and go on with your first patchset.
> 
I pretty much came to the same conclusion. No objections here anymore either.

Guenter

  reply	other threads:[~2010-11-08 16:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22  2:19 [RFC PATCH] include/linux/kernel.h: Add config option for pr_fmt(fmt) Joe Perches
     [not found] ` <alpine.LFD.2.00.1010220131320.7016@localhost.localdomain>
2010-10-22 22:23   ` [PATCH] drivers/acpi: Add and use pr_fmt(fmt) Joe Perches
2010-10-26  9:03 ` [RFC PATCH] include/linux/kernel.h: Add config option for pr_fmt(fmt) Jean Delvare
2010-10-27 17:41   ` Joe Perches
2010-10-28  4:28     ` Guenter Roeck
2010-10-28  7:35     ` Jean Delvare
2010-10-28  7:54       ` Joe Perches
2010-10-28  8:43         ` Jean Delvare
2010-10-29 22:10           ` Joe Perches
2010-11-08 12:33             ` Jean Delvare
2010-11-08 16:55               ` Guenter Roeck [this message]
2010-11-08 17:16                 ` Joe Perches
2010-11-09  3:07                   ` Guenter Roeck
2010-11-09  8:42                     ` Jean Delvare
2010-11-09 16:16                       ` Guenter Roeck

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=20101108165526.GA20229@ericsson.com \
    --to=guenter.roeck@ericsson.com \
    --cc=akpm@linux-foundation.org \
    --cc=joe@perches.com \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@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