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]
Date:	Tue, 26 Apr 2016 10:12:06 +0800
From:	Lu Baolu <baolu.lu@...ux.intel.com>
To:	Mark Brown <broonie@...nel.org>
Cc:	felipe.balbi@...ux.intel.com,
	Mathias Nyman <mathias.nyman@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Lee Jones <lee.jones@...aro.org>,
	Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
	MyungJoo Ham <myungjoo.ham@...sung.com>,
	Chanwoo Choi <cw00.choi@...sung.com>,
	Liam Girdwood <lgirdwood@...il.com>, linux-usb@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 03/10] regulator: fixed: add device binding for
 platform device

Hi Mark,

On 04/26/2016 12:40 AM, Mark Brown wrote:
> On Mon, Apr 25, 2016 at 04:04:49PM +0800, Lu Baolu wrote:
>
>> This is needed to handle the GPIO connected USB vcc pin found on
>> Intel Baytrail devices.
> In what way is this needed?  The we defualt to using the driver name if
> no platform ID table, AFAICT this is just restating the same string?

You are right. This is not a "needed". It just makes the platform
driver binding explicit. We can ignore it if you don't like it.

Best regards,
Lu Baolu

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ