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
| ||
|
Date: Wed, 1 Jun 2011 09:30:00 +0100 From: Russell King - ARM Linux <linux@....linux.org.uk> To: Linus Walleij <linus.walleij@...aro.org> Cc: Mattias Wallin <mattias.wallin@...ricsson.com>, Thomas Gleixner <tglx@...utronix.de>, Lee Jones <lee.jones@...aro.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org> Subject: Re: [PATCH 2/3] clocksource: add DB8500 PRCMU Timer support On Tue, May 31, 2011 at 11:18:25PM +0200, Linus Walleij wrote: > Keeping it under include/linux is probably wise since we want drivers > OUT of the ARM tree, but I don't know if there is much consensus on that? Header files private to a driver should be alongside the driver. Look at drivers/net or drivers/scsi for plenty of examples. Just because its a header file does not mean it must be in some directory with 'include' in its path. The only reason to put it in include/linux is if it contains stuff which needs to be shared outside of the driver (eg, with arches). -- 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/
Powered by blists - more mailing lists