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] [day] [month] [year] [list]
Message-ID: <4FF1C780.9020003@wwwdotorg.org>
Date:	Mon, 02 Jul 2012 10:08:32 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	Liam Girdwood <lrg@...com>, linux-kernel@...r.kernel.org,
	Stephen Warren <swarren@...dia.com>,
	Rob Herring <rob.herring@...xeda.com>,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [PATCH v2] regulator: fixed: support deferred probe for DT GPIOs

On 07/02/2012 10:03 AM, Mark Brown wrote:
> On Mon, Jul 02, 2012 at 09:40:06AM -0600, Stephen Warren wrote:
>> On 07/01/2012 12:23 PM, Mark Brown wrote:
> 
>>> ...this just seems rubbish, why aren't we just fixing the
>>> device tree code and why are we doing this at the device tree
>>> level rather than as a general gpiolib thing?
> 
>> It is being fixed in the DT code:
> 
>> https://lkml.org/lkml/2012/6/18/468
> 
> Is that patch actually being applied (especially with Grant's free
> time issues)?  I've still got the patch sitting in my inbox since
> it wasn't clear what was going on.

It sounds like Rob Herring will be helping out on this for a few
weeks; see:

https://lkml.org/lkml/2012/7/2/3
"Re: SPI, GPIO, and DT maintainer ship (cry for help)"

I cc'd Grant and Rob to make sure.

>> However, it seemed best to make the regulator code work both
>> before and after that patch.
> 
> I'd be kind of inclined to just leave it broken to be honest rather
> than having a huge comment and dodgy code.

Hmmm. That would have made it kinda hard to use:-(
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ