[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F4BA91D.7090303@windriver.com>
Date: Mon, 27 Feb 2012 11:02:37 -0500
From: Paul Gortmaker <paul.gortmaker@...driver.com>
To: James Bottomley <James.Bottomley@...senpartnership.com>
CC: <jejb@...isc-linux.org>, <kyle@...artin.ca>, <deller@....de>,
<linux-parisc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
<linux-next@...r.kernel.org>, <rientjes@...gle.com>,
<xiyou.wangcong@...il.com>
Subject: Re: [PATCH] parisc: fix longstanding build failure on prefetch
On 12-02-27 10:24 AM, James Bottomley wrote:
> On Sun, 2012-02-26 at 15:51 -0500, Paul Gortmaker wrote:
>> Upstream commit e66eed651fd18a961f11cda62f3b5286c8cc4f9f
>>
>> "list: remove prefetching from regular list iterators"
>>
>> removed <linux/prefetch.h> from <linux/list.h> very early in the
>> v3.0 dev cycle (v2.6.39-2-ge66eed6), thereby causing build failures
>> when it exposed the implicit prefetch users in parisc.
>
> I already have this in my internal patch queue:
>
> http://marc.info/?l=linux-parisc&m=132825467010662
Is this in a different queue than what is in linux next?
It would be nice to see such build fixes get into linux-next
ASAP, so folks doing multi-arch coverage builds on their work
can know if they've introduced a regression. At the moment,
the parisc builds in linux-next have been worthless for over
six months, and I'm sure I'm not the 1st one to waste time
"re-solving" old bugs like this.
Thanks,
Paul.
>
> James
>
>
--
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