public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linas@austin.ibm.com, Hollis Blanchard <hollisb@us.ibm.com>,
	nfont@austin.ibm.com, Paul Mackerras <paulus@samba.org>,
	PPC64 External List <linuxppc64-dev@lists.linuxppc.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [2.6] PPC64: log firmware errors during boot.
Date: Fri, 2 Jul 2004 12:44:14 -0700	[thread overview]
Message-ID: <20040702194413.GA13774@kroah.com> (raw)
In-Reply-To: <1088794548.28076.49.camel@nighthawk>

On Fri, Jul 02, 2004 at 11:55:48AM -0700, Dave Hansen wrote:
> On Fri, 2004-07-02 at 11:27, Greg KH wrote:
> > On Fri, Jul 02, 2004 at 01:13:47PM -0500, linas@austin.ibm.com wrote:
> > > I mis-spoke earlier about who the intendend consumers of the printk'ed
> > > messages are; rtasd already implements its own kernl-to-user interface
> > > via the /proc interface.  Yes, everything in /proc/ppc64 is prolly
> > > deprecated, but lets put this off till later.
> > 
> > Later when?
> 
> 2.7.0, anyone?

Fine with me, Linas?


  reply	other threads:[~2004-07-02 19:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30  0:10 [PATCH] [2.6] PPC64: log firmware errors during boot linas
2004-06-30 10:55 ` Paul Mackerras
2004-07-01 21:06   ` linas
2004-07-02  5:36     ` Greg KH
2004-07-02 10:44     ` Paul Mackerras
2004-07-02 14:15       ` Hollis Blanchard
2004-07-02 16:18         ` Nathan Fontenot
2004-07-02 17:29           ` Hollis Blanchard
2004-07-02 18:13             ` linas
2004-07-02 18:27               ` Greg KH
2004-07-02 18:55                 ` Dave Hansen
2004-07-02 19:44                   ` Greg KH [this message]
2004-07-06 13:24             ` Jake Moilanen
2004-07-06 13:41   ` Jake Moilanen
2004-07-08 16:03     ` linas
2004-07-08 17:55       ` Jake Moilanen

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=20040702194413.GA13774@kroah.com \
    --to=greg@kroah.com \
    --cc=haveblue@us.ibm.com \
    --cc=hollisb@us.ibm.com \
    --cc=linas@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc64-dev@lists.linuxppc.org \
    --cc=nfont@austin.ibm.com \
    --cc=paulus@samba.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