linux-kernel - Re: [PATCH v2] GPIO: Add gpio

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]

Message-ID: <20091013162819.02f53284@bike.lwn.net>
Date:	Tue, 13 Oct 2009 16:28:19 -0600
From:	Jonathan Corbet <corbet@....net>
To:	David Brownell <david-b@...bell.net>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH v2] GPIO: Add gpio_lookup

On Tue, 13 Oct 2009 14:10:40 -0700
David Brownell <david-b@...bell.net> wrote:

> Not real keen on this; see separate emails, and below.

OK, so the story I'm getting is that each driver needs to set up its
own mechanism for obtaining GPIO numbers - it needs to create its own
lookup mechanism.  That's fine, I can do that; I just thought it made
sense to make use of the information that's already there.

Andrew, you might as well drop the patch.

(I'm less worried about the uniqueness side, BTW; it just means drivers
need to create meaningful names for their GPIOs.)

Thanks,

jon
--
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/