From: Stephen Warren <swarren@wwwdotorg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Simon Arlott <simon@fire.lp0.eu>, Olof Johansson <olof@lixom.net>,
Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
Chris Boot <bootc@bootc.net>, Dom Cobley <popcornmix@gmail.com>,
Dom Cobley <dc4@broadcom.com>
Subject: Re: linux-next: Tree for Sept 24 (irqchip)
Date: Mon, 24 Sep 2012 10:42:53 -0600 [thread overview]
Message-ID: <50608D8D.4060506@wwwdotorg.org> (raw)
In-Reply-To: <20120925020744.cc5beb9e65473605e5ca2240@canb.auug.org.au>
On 09/24/2012 10:07 AM, Stephen Rothwell wrote:
> Hi Randy,
>
> On Mon, 24 Sep 2012 08:39:05 -0700 Randy Dunlap
> <rdunlap@xenotime.net> wrote:
>>
>> On 09/24/2012 07:53 AM, Stephen Rothwell wrote:
>>
>>> Today was a train wreck, with lots of new conflicts across
>>> several trees and a few build failures as well.
>>
>> I agree. I mostly get this:
>>
>> drivers/Kconfig:157: can't open file "drivers/irqchip/Kconfig"
>>
>> i.e., no such file.
>>
>> How does this happen? :(
>>
>> who handles irqchip?
>
> Hmm, commit 89214f009c1d ("ARM: bcm2835: add interrupt controller
> driver") from the arm-soc tree adds that file as an empty file (I
> have the empty file in my tree). Nothing adds anything to it.
That's odd. I just checked out next-20120924, and that (empty) file
does appear on my disk as expected. Do some versions of git not handle
creating empty files?
Note that IIRC the Kconfig file is required, because otherwise the
build process won't recurse into drivers/irqchip/ and hence code won't
be linked into the kernel image.
The file is empty because the Makefile there keys of
CONFIG_ARCH_BCM2835 and hence doesn't need drivers/irqchip/Kconfig to
define any new Kconfig variables.
next prev parent reply other threads:[~2012-09-24 16:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-24 14:53 linux-next: Tree for Sept 24 Stephen Rothwell
2012-09-24 15:39 ` linux-next: Tree for Sept 24 (irqchip) Randy Dunlap
2012-09-24 16:07 ` Stephen Rothwell
2012-09-24 16:42 ` Stephen Warren [this message]
2012-09-24 16:46 ` Olof Johansson
2012-11-03 1:47 ` Randy Dunlap
2012-09-24 19:50 ` linux-next: Tree for Sept 24 (net/ipv4) Randy Dunlap
2012-09-24 22:02 ` linux-next: Tree for Sept 24 (iommu) Randy Dunlap
2012-09-25 3:23 ` Alex Williamson
2012-09-25 10:16 ` Roedel, Joerg
2012-09-24 22:10 ` linux-next: Tree for Sept 24 (remoteproc) Randy Dunlap
2012-09-30 8:33 ` Ohad Ben-Cohen
2012-10-01 23:16 ` Randy Dunlap
2012-10-02 8:04 ` Ohad Ben-Cohen
2012-09-24 22:25 ` linux-next: Tree for Sept 24 (net without INET) Randy Dunlap
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=50608D8D.4060506@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--cc=bootc@bootc.net \
--cc=dc4@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--cc=popcornmix@gmail.com \
--cc=rdunlap@xenotime.net \
--cc=sfr@canb.auug.org.au \
--cc=simon@fire.lp0.eu \
/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).