From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: JBottomley@parallels.com, jejb@parisc-linux.org,
kyle@mcmartin.ca, deller@gmx.de
Cc: linux-parisc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-next@vger.kernel.org, rientjes@google.com,
xiyou.wangcong@gmail.com,
Paul Gortmaker <paul.gortmaker@windriver.com>
Subject: [PATCH] parisc: fix longstanding build failure on prefetch
Date: Sun, 26 Feb 2012 15:51:18 -0500 [thread overview]
Message-ID: <1330289478-12603-1-git-send-email-paul.gortmaker@windriver.com> (raw)
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.
Reported-by: David Rientjes <rientjes@google.com>
Reported-by: WANG Cong <xiyou.wangcong@gmail.com>
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
---
[ The parisc defconfig has been failing to build everywhere since
last May! http://kisskb.ellerman.id.au/kisskb/target/2059/ And this
one liner fix https://lkml.org/lkml/2011/10/15/121 was reported last
Oct, and again http://www.spinics.net/lists/linux-parisc/msg03945.html
in early Feb. So, now with a clear reasoning in the commit header as
to why it fails, can we finally get this in tree please? ]
diff --git a/drivers/parisc/iommu-helpers.h b/drivers/parisc/iommu-helpers.h
index a9c46cc..8c33491 100644
--- a/drivers/parisc/iommu-helpers.h
+++ b/drivers/parisc/iommu-helpers.h
@@ -1,3 +1,5 @@
+#include <linux/prefetch.h>
+
/**
* iommu_fill_pdir - Insert coalesced scatter/gather chunks into the I/O Pdir.
* @ioc: The I/O Controller.
--
1.7.9.1
next reply other threads:[~2012-02-26 20:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 20:51 Paul Gortmaker [this message]
2012-02-27 15:24 ` [PATCH] parisc: fix longstanding build failure on prefetch James Bottomley
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=1330289478-12603-1-git-send-email-paul.gortmaker@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=JBottomley@parallels.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox