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: Tue, 7 Aug 2012 11:34:43 +0000 From: Arnd Bergmann <arnd@...db.de> To: Russell King <rmk@....linux.org.uk> Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>, Mark Brown <broonie@...nsource.wolfsonmicro.com>, Haojian Zhuang <haojian.zhuang@...il.com>, sameo@...ux.intel.com, rpurdie@...ys.net, bryan.wu@...onical.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/5] mfd: replace IORESOURCE_IO by IORESOURCE_MEM On Tuesday 07 August 2012, Russell King wrote: > On Tue, Aug 07, 2012 at 11:28:27AM +0000, Arnd Bergmann wrote: > > If we introduce a new IORESOURCE_OTHER, I would actually prefer to > > define it to 0x00000000 for purely aesthetic reasons, the effect > > should be the same as using 0x00000300. > > I'd suggest not, because we can use that to detect uninitialized > resources (and we probably do so in some places.) IOW, I think that's > asking for problems when this moves outside platform code. Good point. Let's use 0x00000300 then. Arnd -- 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