linux-kernel - Re: [v2 2/4] platform: (TS-5500) add GPIO support

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Tue, 30 Aug 2011 16:12:18 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Cc:	"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org,
	Jerome Oufella <jerome.oufella@...oirfairelinux.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [v2 2/4] platform: (TS-5500) add GPIO support

On Tue, Aug 30, 2011 at 10:49:55AM -0400, Vivien Didelot wrote:
> Mark Brown <broonie@...nsource.wolfsonmicro.com> wrote:

> > > Should they?  It seems a lot more reasonable to have them collected
> > > by platform than by type of device (GPIO), *unless* they are shared.

> Grouping every driver for this platform was one of the main comments of
> my first RFC set of patches. And indeed, the GPIO driver is really
> specific to this platform, so it won't be shared.

That's the case for a lot of the ARM ones too, the same considerations
apply there.  There's generally a problem with people working needlessly
in isolation and a fairly low burden for subsystem maintainers.
--
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/