linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Walleij <linus.walleij@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Fabian Vogt <fabian@ritter-vogt.de>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the final tree (gpio tree related)
Date: Wed, 5 Mar 2014 15:16:02 +0800	[thread overview]
Message-ID: <CACRpkda8qHQRu-JCgdVOHAh+QvjfJB5ftJEEQ66tjePrRCuYzA@mail.gmail.com> (raw)
In-Reply-To: <20140305173559.0b50971a1ab88a16bee8819c@canb.auug.org.au>

On Wed, Mar 5, 2014 at 2:35 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:

> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/gpio/gpio-zevio.c: In function 'zevio_gpio_port_get':
> drivers/gpio/gpio-zevio.c:70:2: error: implicit declaration of function 'IOMEM' [-Werror=implicit-function-declaration]
>   return readl(IOMEM(c->chip.regs + section_offset + port_offset));
>   ^
> drivers/gpio/gpio-zevio.c:70:2: warning: passing argument 1 of 'readl' makes pointer from integer without a cast [enabled by default]
> In file included from include/linux/io.h:22:0,
>                  from drivers/gpio/gpio-zevio.c:15:
> arch/powerpc/include/asm/io-defs.h:6:16: note: expected 'const volatile void *' but argument is of type 'int'
>  DEF_PCI_AC_RET(readl, u32, (const PCI_IO_ADDR addr), (addr), mem, addr)
>                 ^

Fabian can you suggest a patch adding the proper depends added to
the Kconfig. Check what things bring in the IOMEM etc that is needed
to compile this.

Yours,
Linus Walleij

  reply	other threads:[~2014-03-05  7:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  6:35 linux-next: build failure after merge of the final tree (gpio tree related) Stephen Rothwell
2014-03-05  7:16 ` Linus Walleij [this message]
2014-03-05 16:42   ` Fabian Vogt
  -- strict thread matches above, loose matches on Subject: below --
2013-12-23  4:54 Stephen Rothwell
2013-10-29  9:10 Stephen Rothwell
2013-10-29 13:25 ` Linus Walleij
2013-10-30  0:56   ` Alex Courbot
2013-10-28 14:12 Stephen Rothwell
2013-10-29 13:28 ` Linus Walleij
2012-02-06  4:23 Stephen Rothwell
2012-02-06  6:07 ` Grant Likely
2012-02-06 14:02   ` Mark Brown

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=CACRpkda8qHQRu-JCgdVOHAh+QvjfJB5ftJEEQ66tjePrRCuYzA@mail.gmail.com \
    --to=linus.walleij@linaro.org \
    --cc=fabian@ritter-vogt.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).