From: "Samuel Iglesias Gonsálvez" <siglesias@igalia.com>
To: Jens Taprogge <jens.taprogge@taprogge.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
industrypack-devel@lists.sourceforge.net,
Greg KH <greg@kroah.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] staging: ipack: only build on platforms that provide ioread/iowrite.
Date: Fri, 07 Sep 2012 09:01:32 +0200 [thread overview]
Message-ID: <1347001292.5957.43.camel@fourier.local.igalia.com> (raw)
In-Reply-To: <1346960719-9184-2-git-send-email-jens.taprogge@taprogge.org>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On Thu, 2012-09-06 at 21:45 +0200, Jens Taprogge wrote:
> Do so by depending on HAS_IOMEM.
>
> Reported-by: Geert Uytterhoeven <geert@linux-m68k.org>
>
> Signed-off-by: Jens Taprogge <jens.taprogge@taprogge.org>
> ---
> drivers/staging/ipack/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/staging/ipack/Kconfig b/drivers/staging/ipack/Kconfig
> index af32178..4cf4706 100644
> --- a/drivers/staging/ipack/Kconfig
> +++ b/drivers/staging/ipack/Kconfig
> @@ -4,6 +4,7 @@
>
> menuconfig IPACK_BUS
> tristate "IndustryPack bus support"
> + depends on HAS_IOMEM
> ---help---
> If you say Y here you get support for the IndustryPack Framework
> for drivers for many types of boards that support this industrial
Acked-by: Samuel Iglesias Gonsálvez <siglesias@igalia.com>
Thanks,
Sam
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-09-07 7:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 5:48 linux-next: build failure after merge of the final tree (staging tree related) Stephen Rothwell
2012-09-05 7:08 ` [PATCH] Staging: ipack: fix build failure in powerpc allyesconfig Samuel Iglesias Gonsálvez
2012-09-06 18:06 ` linux-next: build failure after merge of the final tree (staging tree related) Geert Uytterhoeven
[not found] ` <1346960719-9184-1-git-send-email-jens.taprogge@taprogge.org>
[not found] ` <1346960719-9184-2-git-send-email-jens.taprogge@taprogge.org>
2012-09-07 7:01 ` Samuel Iglesias Gonsálvez [this message]
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=1347001292.5957.43.camel@fourier.local.igalia.com \
--to=siglesias@igalia.com \
--cc=geert@linux-m68k.org \
--cc=greg@kroah.com \
--cc=industrypack-devel@lists.sourceforge.net \
--cc=jens.taprogge@taprogge.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).