linux-kernel - Re: [PATCH] FRV: Hook up gpiolib 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] [day] [month] [year] [list]

Message-ID: <20110617121845.GA18493@opensource.wolfsonmicro.com>
Date:	Fri, 17 Jun 2011 13:18:45 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	David Howells <dhowells@...hat.com>
Cc:	linux-kernel@...r.kernel.org, grant@...retlab.ca,
	ralf@...ux-mips.org
Subject: Re: [PATCH] FRV: Hook up gpiolib support

On Fri, Jun 17, 2011 at 11:50:59AM +0100, David Howells wrote:
> Okay:

Thanks, this is a lot more constructive.  I'm now wondering how anyone
has managed to use this header (which isn't exactly new or only used on
obscure architectures) without noticing and fixing this.

It's unlikely that I'm going to have the bandwidth to work on the cross
tree issues that sorting this would create in the immediate future, my
interest here is in stopping people bugging me about architectures that
don't keep up with the standard GPIO interface but it'd be good if
someone could do so.
--
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/