Date: Sun, 6 Jan 2008 13:38:17 -0800
From: Arjan van de Ven <arjan@infradead.org>
To: Olof Johansson <olof@lixom.net>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
       heiko.carstens@de.ibm.com, mingo@elte.hu, mpm@selenic.com
Subject: Re: [PATCH] Add bug/warn marker to generic report_bug()
Message-ID: <20080106133817.4f42ab82@laptopd505.fenrus.org>
In-Reply-To: <20080106202223.GA12640@lixom.net>
References: <20080105190713.73745ec6@laptopd505.fenrus.org>
	<20080106202223.GA12640@lixom.net>
Organization: Intel
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 813
Lines: 19

On Sun, 6 Jan 2008 14:22:23 -0600
Olof Johansson <olof@lixom.net> wrote:

> Powerpc uses the generic report_bug() from lib/bug.c to report
> warnings, and I'm guessing other arches do as well.
> 
> Add the module list as well as the end-of-trace marker to the output.
> This required making print_oops_end_marker() nonstatic.
> 
> 

this is the wrong approach...
powerpc and such should just use oops_enter() / oops_exit() to signal the start/end of such 
a trace, that gives them all the other behavior of oopsing as well (such as the "slow oops scrolling down" etc)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/