From: James Bottomley <James.Bottomley@HansenPartnership•com>
To: Paul Gortmaker <paul.gortmaker@windriver•com>
Cc: jejb@parisc-linux•org, kyle@mcmartin•ca, deller@gmx•de,
linux-parisc@vger•kernel.org, mst@redhat•com,
linux-kernel@vger•kernel.org, linux-next@vger•kernel.org,
Randy Dunlap <rdunlap@xenotime•net>
Subject: Re: [PATCH] parisc: fix longstanding build failures for !CONFIG_PCI
Date: Mon, 27 Feb 2012 09:20:57 -0600 [thread overview]
Message-ID: <1330356057.2822.44.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <1330298677-17205-1-git-send-email-paul.gortmaker@windriver.com>
On Sun, 2012-02-26 at 18:24 -0500, Paul Gortmaker wrote:
> Upstream commit fea80311a939a746533a6d7e7c3183729d6a3faf
>
> "iomap: make IOPORT/PCI mapping functions conditional"
>
> introduced an arch independent stub for pci_iounmap() but the
> parisc had its own that was unconditionally built. So builds
> since v3.0-3553-gfea8031 have been failing with:
>
> arch/parisc/lib/iomap.c:439:6: error: redefinition of 'pci_iounmap'
> include/asm-generic/iomap.h:75:20: note: previous definition of 'pci_iounmap' was here
>
> Making the parisc one specific to CONFIG_PCI fixes the problem.
>
> CC: Randy Dunlap <rdunlap@xenotime•net>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver•com>
> ---
>
> [This fixes the linux-next builds that have been consistently failing
> since last July -- http://kisskb.ellerman.id.au/kisskb/target/2069/ ]
>
> diff --git a/arch/parisc/lib/iomap.c b/arch/parisc/lib/iomap.c
> index fb8e10a..dc0a2c3 100644
> --- a/arch/parisc/lib/iomap.c
> +++ b/arch/parisc/lib/iomap.c
This should break more than just PARISC ... any non-PCI build for any
arch should be broken, so this is the proposed generic fix:
http://marc.info/?l=linux-parisc&m=132794183521355
James
next prev parent reply other threads:[~2012-02-27 15:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-26 23:24 [PATCH] parisc: fix longstanding build failures for !CONFIG_PCI Paul Gortmaker
2012-02-27 15:20 ` James Bottomley [this message]
2012-02-27 16:12 ` Paul Gortmaker
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=1330356057.2822.44.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership$(echo .)com \
--cc=deller@gmx$(echo .)de \
--cc=jejb@parisc-linux$(echo .)org \
--cc=kyle@mcmartin$(echo .)ca \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=linux-parisc@vger$(echo .)kernel.org \
--cc=mst@redhat$(echo .)com \
--cc=paul.gortmaker@windriver$(echo .)com \
--cc=rdunlap@xenotime$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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