[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061020183159.GB8894@flint.arm.linux.org.uk>
Date: Fri, 20 Oct 2006 19:31:59 +0100
From: Russell King <rmk+lkml@....linux.org.uk>
To: Andrew Morton <akpm@...l.org>
Cc: Adrian Bunk <bunk@...sta.de>, Linus Torvalds <torvalds@...l.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [0/3] 2.6.19-rc2: known regressions
On Fri, Oct 20, 2006 at 11:19:00AM -0700, Andrew Morton wrote:
> On Fri, 20 Oct 2006 19:07:22 +0100
> Russell King <rmk+lkml@....linux.org.uk> wrote:
>
> > > > Subject : undefined reference to highest_possible_node_id
> > > > References : http://lkml.org/lkml/2006/9/4/233
> > > > http://lkml.org/lkml/2006/10/15/11
> > > > Submitter : Olaf Hering <olaf@...fle.de>
> > > > Caused-By : Greg Banks <gnb@...bourne.sgi.com>
> > > > commit 0f532f3861d2c4e5aa7dcd33fb18e9975eb28457
> > > > Status : unknown
> > >
> > > Looking at this commit and the mails, it was known on the 4th September
> > > that this patch caused build errors while this change was in -mm, yet it
> > > still found its way into mainline on 2nd October.
> > >
> > > Is anyone going to look at fixing this problem, or should we be asking
> > > for the commit to be reverted?
> >
> > Since everyone seems intent at ignoring this issue, here's a patch to
> > try to solve it.
>
> I sent the below to Linus yesterday...
Ah, okay. Must not have poped out of the other side of Linus by 6am GMT
then. (We also seem to have non-working git snapshots again, so when I
looked at the ARM kautobuild it showed the same old errors.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists