On Mon, Apr 14, 2008 at 11:48:23AM +1000, Stephen Rothwell wrote:
quoted text
> Hi Greg,
> 
> On Thu, 10 Apr 2008 21:34:00 +0200 Mariusz Kozlowski <m.kozlowski@tuxland.pl> wrote:
> >
> > 	The commit b818da52 makes my sparc64 box simply unable to boot.
> > You should probably take a look at other arches as well. The story is here:
> > 
> > http://lkml.org/lkml/2008/3/28/465
> > http://lkml.org/lkml/2008/4/1/248
> 
> This patch has remained unchanged since first imported into linux-next in
> March 6.
> 
> So, the question is: What are the consequences of reverting it?  I am not
> in a position to judge, but if it causes boxes to simply not boot, then
> it would be a major regression in 2.6.26 and simply cannot be included
> there.
> 
> I will revert it at the end of today's tree and hope that there is some
> resolution before the merge window opens.
> 
> Of course, there is still the question of the other architectures ...

Yes, I haven't caught up with my emails, but yes, this will not go
upstream for those arches that have had problems with it (like sparc64).
I'll fix my tree up first thing Monday morning for this issue.

Sorry for taking so long with it, been stuck doing other things...

thanks,

greg k-h
--
unsubscribe notice
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/