From: Jean Delvare <khali@linux-fr.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Joe Perches <joe@perches.com>,
linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
adaplas@pol.net, greg@kroah.com, jeff@garzik.org
Subject: Re: + remove-current-defines-and-uses-of-pr_err-add-pr_emerg.patch added to -mm tree
Date: Wed, 8 Aug 2007 22:02:26 +0200 [thread overview]
Message-ID: <20070808220226.1dc03a67@hyperion.delvare> (raw)
In-Reply-To: <20070807131949.fa060048.akpm@linux-foundation.org>
On Tue, 7 Aug 2007 13:19:49 -0700, Andrew Morton wrote:
> On Fri, 03 Aug 2007 15:16:09 -0700
> Joe Perches <joe@perches.com> wrote:
>
> > On Fri, 2007-08-03 at 17:05 +0200, Jean Delvare wrote:
> > > Fine with me, but this first patch should still be correct per se.
> >
> > Add new pr_<level> printk(KERN_<level> fmt "\n", ##arg) to kernel.h
> > pr_info and pr_debug are unchanged
> > Remove local pr_err #defines
> > Convert current uses of pr_err
>
> OK, I've lost the plot here. If we have now converged on an
> agreeable patch, please resend it?
I don't think we have, no. It's not even clear what Joe is trying to
achieve.
--
Jean Delvare
next prev parent reply other threads:[~2007-08-08 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tI4NY5SL.1186153543.0764100.khali@localhost>
2007-08-03 22:16 ` + remove-current-defines-and-uses-of-pr_err-add-pr_emerg.patch added to -mm tree Joe Perches
2007-08-04 9:43 ` Jan Engelhardt
2007-08-04 16:47 ` Jean Delvare
2007-08-07 16:10 ` Joe Perches
2007-08-07 16:16 ` Jan Engelhardt
2007-08-07 20:19 ` Andrew Morton
2007-08-08 20:02 ` Jean Delvare [this message]
2007-08-08 20:31 ` Joe Perches
2007-08-08 20:39 ` Jan Engelhardt
2007-08-08 21:36 ` Joe Perches
2007-08-08 21:57 ` Jan Engelhardt
2007-08-08 22:21 ` Joe Perches
2007-08-10 20:22 ` Jean Delvare
2007-08-01 22:27 akpm
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=20070808220226.1dc03a67@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=adaplas@pol.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.