linux-kernel - Re: [PATCH 1/2] regulator: fixed: use devm

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4FF2B1D7.30205@nvidia.com>
Date:	Tue, 3 Jul 2012 14:18:23 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
CC:	"lrg@...com" <lrg@...com>,
	"grant.likely@...retlab.ca" <grant.likely@...retlab.ca>,
	"rob.herring@...xeda.com" <rob.herring@...xeda.com>,
	"rob@...dley.net" <rob@...dley.net>,
	"devicetree-discuss@...ts.ozlabs.org" 
	<devicetree-discuss@...ts.ozlabs.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/2] regulator: fixed: use devm_* for gpio request

On Monday 02 July 2012 10:59 PM, Mark Brown wrote:
> * PGP Signed by an unknown key
>
> On Mon, Jul 02, 2012 at 03:37:24PM +0530, Laxman Dewangan wrote:
>> Use devm_* version of gpio APIs gpio_request_one() for
>> requesting gpios.
>> This avoid extra code for freeing gpios.
> This can't be applied yet since the export for the devm version hasn't
> been applied so it won't build and also conflicts with the factoring out
> of the GPIO code to the core.
>
Oops, then lets ignore the 1/2 for now. If require, we will revisit later.

But what about 2/2? Does it look good? I can send that as separate patch 
if it is fine.


--
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/