From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: jejb@parisc-linux.org, kyle@mcmartin.ca, deller@gmx.de,
linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, rientjes@google.com,
xiyou.wangcong@gmail.com
Subject: Re: [PATCH] parisc: fix longstanding build failure on prefetch
Date: Mon, 27 Feb 2012 11:02:37 -0500 [thread overview]
Message-ID: <4F4BA91D.7090303@windriver.com> (raw)
In-Reply-To: <1330356289.2822.45.camel@dabdike.int.hansenpartnership.com>
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
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: James Bottomley <James.Bottomley@hansenpartnership.com>
Cc: <jejb@parisc-linux.org>, <kyle@mcmartin.ca>, <deller@gmx.de>,
<linux-parisc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-next@vger.kernel.org>, <rientjes@google.com>,
<xiyou.wangcong@gmail.com>
Subject: Re: [PATCH] parisc: fix longstanding build failure on prefetch
Date: Mon, 27 Feb 2012 11:02:37 -0500 [thread overview]
Message-ID: <4F4BA91D.7090303@windriver.com> (raw)
In-Reply-To: <1330356289.2822.45.camel@dabdike.int.hansenpartnership.com>
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
>
>
next prev parent reply other threads:[~2012-02-27 16:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 20:51 [PATCH] parisc: fix longstanding build failure on prefetch Paul Gortmaker
2012-02-27 15:24 ` James Bottomley
2012-02-27 16:02 ` Paul Gortmaker [this message]
2012-02-27 16:02 ` Paul Gortmaker
2012-02-27 16:32 ` James Bottomley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F4BA91D.7090303@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=deller@gmx.de \
--cc=jejb@parisc-linux.org \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=rientjes@google.com \
--cc=xiyou.wangcong@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.