From: Mark Brown <broonie@opensource•wolfsonmicro.com>
To: Grant Likely <grant.likely@secretlab•ca>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
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: Mon, 6 Feb 2012 14:02:13 +0000 [thread overview]
Message-ID: <20120206140213.GC10173@sirena.org.uk> (raw)
In-Reply-To: <20120206060708.GC21449@ponder.secretlab.ca>
On Sun, Feb 05, 2012 at 11:07:08PM -0700, Grant Likely wrote:
> On Mon, Feb 06, 2012 at 03:23:46PM +1100, Stephen Rothwell wrote:
> > 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'
> 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.
IIRC I saw a similar issue trying to build the twl-core driver on
Samsung platforms (or possibly x86).
next prev parent reply other threads:[~2012-02-06 14:02 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
2012-02-06 14:02 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
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=20120206140213.GC10173@sirena.org.uk \
--to=broonie@opensource$(echo .)wolfsonmicro.com \
--cc=bigeasy@linutronix$(echo .)de \
--cc=grant.likely@secretlab$(echo .)ca \
--cc=hjk@linutronix$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=torbenh@linutronix$(echo .)de \
/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