From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.ozlabs.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org,
Lennert Buytenhek <buytenh@secretlab.ca>,
Grant Likely <grant.likely@secretlab.ca>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: linux-next: build failure after merge of the final tree (powerpc tree related)
Date: Tue, 15 Mar 2011 07:37:54 +1100 [thread overview]
Message-ID: <1300135074.22236.788.camel@pasglop> (raw)
In-Reply-To: <20110314203827.4b61818e.sfr@canb.auug.org.au>
On Mon, 2011-03-14 at 20:38 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/gpio/langwell_gpio.c: In function 'lnw_irq_handler':
> drivers/gpio/langwell_gpio.c:210: error: 'struct irq_desc' has no member named 'chip'
> drivers/gpio/langwell_gpio.c:211: error: 'struct irq_desc' has no member named 'chip'
>
> Caused by commit 17b9f9e2653a ("powerpc: Enable
> GENERIC_HARDIRQS_NO_DEPRECATED") enabling
> CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED for powerpc without previously
> fixing up the above driver.
>
> I have reverted that commit for today.
Except that the above driver has nothing to do with powerpc, it's some
Intel Moorestown stuff...
It should be fixed regardless I suppose, CC'ing Thomas.
Cheers,
Ben.
next prev parent reply other threads:[~2011-03-14 20:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 9:38 linux-next: build failure after merge of the final tree (powerpc tree related) Stephen Rothwell
2011-03-14 20:37 ` Benjamin Herrenschmidt [this message]
2011-03-14 20:51 ` David Miller
2011-03-14 21:17 ` Thomas Gleixner
2011-03-14 21:21 ` Lennert Buytenhek
-- strict thread matches above, loose matches on Subject: below --
2013-12-09 6:32 Stephen Rothwell
2013-01-11 5:52 Stephen Rothwell
2013-01-11 6:04 ` Michael Neuling
2012-09-06 7:11 Stephen Rothwell
2012-09-06 8:20 ` Ananth N Mavinakayanahalli
2011-06-30 6:36 Stephen Rothwell
2011-06-30 7:09 ` Benjamin Herrenschmidt
2011-05-05 3:41 Stephen Rothwell
2010-12-03 5:32 Stephen Rothwell
2010-12-03 5:59 ` Benjamin Herrenschmidt
2010-12-03 6:08 ` Stephen Rothwell
2010-12-03 11:26 ` Josh Boyer
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=1300135074.22236.788.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=buytenh@secretlab.ca \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=paulus@samba.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@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).