| 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
| ||
|
Message-ID: <20140602153941.GA11004@atomide.com> Date: Mon, 2 Jun 2014 08:39:41 -0700 From: Tony Lindgren <tony@...mide.com> To: Stephen Warren <swarren@...dotorg.org> Cc: FanWu <fwu@...vell.com>, "linus.walleij@...aro.org" <linus.walleij@...aro.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "swarren@...dia.com" <swarren@...dia.com>, Chao Xie <cxie4@...vell.com>, Yilu Mao <ylmao@...vell.com>, Ning Jiang <njiang1@...vell.com>, Xiaofan Tian <tianxf@...vell.com>, Fangsuo Wu <fswu@...vell.com> Subject: Re: [PATCH v2] pinctrl: add params in disable_setting for different usage * Stephen Warren <swarren@...dotorg.org> [140523 09:16]: > On 05/22/2014 07:54 PM, FanWu wrote: > > the pinctrl-single driver is still using ops->disable, if I remove the > > "disable" in ops, there will be build error in the vendor's code base > > who is using pinctrl-single driver. > > I thought Tony said it was fine to simply remove pinctrl-single's > ops->disable code completeley. AFAIK nobody is using it. At least we don't have any references to pinctrl-single,function-off property in the .dts files. So removing pcs_disable seems safe to do, the property we probably want to parse and produce a warning in case somebody is using it out of tree. Regards, Tony -- 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