From: Grant Likely <grant.likely@secretlab.ca>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
"Hans J. Koch" <hjk@linutronix.de>,
Torben Hohn <torbenh@linutronix.de>
Subject: Re: linux-next: build failure after merge of the final tree (gpio tree related)
Date: Sun, 5 Feb 2012 23:07:08 -0700 [thread overview]
Message-ID: <20120206060708.GC21449@ponder.secretlab.ca> (raw)
In-Reply-To: <20120206152346.106057d7dd747d0daa47bbc8@canb.auug.org.au>
On Mon, Feb 06, 2012 at 03:23:46PM +1100, Stephen Rothwell wrote:
> Hi Grant,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/gpio/gpio-sodaville.c:130:2: error: unknown field 'dt_translate' specified in initializer
> drivers/gpio/gpio-sodaville.c:130:2: warning: initialization from incompatible pointer type [enabled by default]
> drivers/gpio/gpio-sodaville.c:130:2: warning: (near initialization for 'irq_domain_sdv_ops.match') [enabled by default]
> drivers/gpio/gpio-sodaville.c: In function 'sdv_register_irqsupport':
> drivers/gpio/gpio-sodaville.c:152:8: error: 'struct irq_domain' has no member named 'irq_base'
> drivers/gpio/gpio-sodaville.c:182:2: error: implicit declaration of function 'irq_domain_add' [-Werror=implicit-function-declaration]
> drivers/gpio/gpio-sodaville.c: In function 'sdv_gpio_remove':
> drivers/gpio/gpio-sodaville.c:263:2: error: implicit declaration of function 'irq_domain_del' [-Werror=implicit-function-declaration]
>
> Caused by commit 8b26c833d229 ("gpio: Add a driver for Sodaville GPIO
> controller") interacting with the irqdomain tree changes.
>
> I have reverted that commit for today. I am not sure how you should
> handle this ... you could send me a fixup patch that I should apply as a
> merge fix when merging the irqdomain tree.
The sodavile is an x86 driver only. This problem can be solved by
making it depend on x86, which I'll do now. When x86 is converted to the
new irq_domain code the problem will go even further away.
g.
next prev parent reply other threads:[~2012-02-06 6:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 4:23 linux-next: build failure after merge of the final tree (gpio tree related) Stephen Rothwell
2012-02-06 6:07 ` Grant Likely [this message]
2012-02-06 14:02 ` Mark Brown
2013-10-28 14:12 Stephen Rothwell
2013-10-29 13:28 ` Linus Walleij
2013-10-29 9:10 Stephen Rothwell
2013-10-29 13:25 ` Linus Walleij
2013-10-30 0:56 ` Alex Courbot
2013-12-23 4:54 Stephen Rothwell
2014-03-05 6:35 Stephen Rothwell
2014-03-05 7:16 ` Linus Walleij
2014-03-05 16:42 ` Fabian Vogt
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=20120206060708.GC21449@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=bigeasy@linutronix.de \
--cc=hjk@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torbenh@linutronix.de \
/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).