| 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, 22 Jan 2013 09:55:32 +0100 From: Linus Walleij <linus.walleij@...aro.org> To: Alex Courbot <acourbot@...dia.com>, Steven King <sfking@...dc.com> Cc: Greg Ungerer <gerg@...inux.org>, Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven <geert@...ux-m68k.org>, Grant Likely <grant.likely@...retlab.ca>, Guenter Roeck <linux@...ck-us.net>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-arch <linux-arch@...r.kernel.org>, "linux-arm-kernel@...ts.infradead.org" <linux-arm-kernel@...ts.infradead.org>, "devicetree-discuss@...ts.ozlabs.org" <devicetree-discuss@...ts.ozlabs.org>, gnurou@...il.com Subject: Re: [PATCH 0/4] gpio: introduce descriptor-based interface On Sun, Jan 20, 2013 at 7:07 AM, Alex Courbot <acourbot@...dia.com> wrote: > Actually the question of switching to GPIOlib is only worth being asked if > you are making use of drivers that require GENERIC_GPIO. If this is not the > case and your GPIOs are only used by your own platform code, you can always > give up using defining GENERIC_GPIO and continue implementing them your own > way. Agreed. The problem can be summed up like this: #include <linux/gpio.h> Considered ambiguous. #include <asm/foo/bar/baz-gpio.h> OK with me. Yours, Linus Walleij -- 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