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: Wed, 29 Mar 2017 03:43:48 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: jacopo <jacopo@...ndi.org> Cc: Jacopo Mondi <jacopo+renesas@...ndi.org>, Geert Uytterhoeven <geert+renesas@...der.be>, Laurent Pinchart <laurent.pinchart@...asonboard.com>, Chris Brandt <chris.brandt@...esas.com>, Rob Herring <robh+dt@...nel.org>, Mark Rutland <mark.rutland@....com>, Russell King <linux@...linux.org.uk>, Linux-Renesas <linux-renesas-soc@...r.kernel.org>, "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>, "devicetree@...r.kernel.org" <devicetree@...r.kernel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org> Subject: Re: [PATCH v3 1/7] pinctrl: Renesas RZ/A1 pin and gpio controller On Fri, Mar 24, 2017 at 5:45 PM, jacopo <jacopo@...ndi.org> wrote: > I initially created a whole new sub-directory where all the Renesas > devices with this kind of pin controller would have gone > (drivers/pinctrl/rz-pfc) but since as of now the only available > hardware of that type is RZ/A1 and some of its variants, we decided to go > with a single driver supporting that platform only. > If more will come, we'll think about supporting them through this > driver if possible, or create a dedicated directory. > > Are you ok with this? Yep it's OK. It's no big deal to move it into a new subdir if many new drivers start popping in anyway. Right now I see the use of renesas,pins as the only big blocker, I would much like it to use just pins = <>; Yours, Linus Walleij
Powered by blists - more mailing lists