linux-kernel - Re: [RFC PATCH] gpiolib: Provide and export gpiod_export

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 for Android: free password hash cracker in your pocket

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

Date:	Mon, 11 Aug 2014 15:05:54 -0700
From:	Alexandre Courbot <gnurou@...il.com>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Randy Dunlap <rdunlap@...radead.org>
Subject: Re: [RFC PATCH] gpiolib: Provide and export gpiod_export_name

On Mon, Aug 11, 2014 at 9:13 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> On 08/11/2014 08:20 AM, Alexandre Courbot wrote:
> [ ... ]
>
>>
>> Note that this doesn't change anything to the core of the argument ;
>> we have not heard what Linus thinks about named GPIOs in
>> /sys/class/gpio yet, maybe he will have a different opinion...
>>
>
> Well, please let me know if/when you are planning to take away
> that existing ABI so I can plan accordingly. FWIW, out-of-kernel
> users I am currently aware of are Juniper Networks and Zodiac
> Aerospace. The latter asked me to help them upstreaming their code.
>
> If you plan to remove the ABI, you might want to inform its current
> in-kernel users. You can look those up yourself.

We are not taking existing user-space ABIs away. But we are also not
encouraging people to use bad ABIs by introducing new ways to use
them, hence my restraint towards this patch.
--
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/