From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S264788AbUGBS4Z@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S264788AbUGBS4Z (ORCPT <rfc822;willy@w.ods.org>);
	Fri, 2 Jul 2004 14:56:25 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264795AbUGBS4Z
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Fri, 2 Jul 2004 14:56:25 -0400
Received: from e2.ny.us.ibm.com ([32.97.182.102]:31699 "EHLO e2.ny.us.ibm.com")
	by vger.kernel.org with ESMTP id S264788AbUGBS4X (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 2 Jul 2004 14:56:23 -0400
Subject: Re: [PATCH] [2.6] PPC64: log firmware errors during boot.
From: Dave Hansen <haveblue@us.ibm.com>
To: Greg KH <greg@kroah.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>
In-Reply-To: <20040702182752.GA28825@kroah.com>
References: <20040629191046.Q21634@forte.austin.ibm.com>
	 <16610.39955.554139.858593@cargo.ozlabs.ibm.com>
	 <20040701160614.I21634@forte.austin.ibm.com>
	 <16613.15510.325099.273419@cargo.ozlabs.ibm.com>
	 <3EC84E0C-CC32-11D8-BDBD-000A95A0560C@us.ibm.com>
	 <40E58AE9.6050009@austin.ibm.com> <1088789345.26946.9.camel@localhost>
	 <20040702131347.V21634@forte.austin.ibm.com>
	 <20040702182752.GA28825@kroah.com>
Content-Type: text/plain
Message-Id: <1088794548.28076.49.camel@nighthawk>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.6 
Date: Fri, 02 Jul 2004 11:55:48 -0700
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

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?

I think it would be nice to put printk()s in /proc/ppc64 handler
functions in early 2.7 and print out the task names along with a message
asking the user to report them.  That way, we can more easily track down
all of the users.  

The code would come back out before the next stable kernel.  

-- Dave