linux-kernel - Re: linux-next: Tree for Sept 24 (irqchip)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <50608D8D.4060506@wwwdotorg.org>
Date:	Mon, 24 Sep 2012 10:42:53 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
CC:	Randy Dunlap <rdunlap@...otime.net>, linux-next@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	Simon Arlott <simon@...e.lp0.eu>,
	Olof Johansson <olof@...om.net>, Arnd Bergmann <arnd@...db.de>,
	linux-arm-kernel@...ts.infradead.org, Chris Boot <bootc@...tc.net>,
	Dom Cobley <popcornmix@...il.com>,
	Dom Cobley <dc4@...adcom.com>
Subject: Re: linux-next: Tree for Sept 24 (irqchip)

On 09/24/2012 10:07 AM, Stephen Rothwell wrote:
> Hi Randy,
> 
> On Mon, 24 Sep 2012 08:39:05 -0700 Randy Dunlap
> <rdunlap@...otime.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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/