linux-kernel - Re: [PATCH 7/7] regulator: ti-abb: Use devm_regulator

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: <CAK9yfHzq5isoj0bv405DNF_E=u0nKBBVscbcuoHT-8PxVaserA@mail.gmail.com>
Date:	Wed, 4 Sep 2013 22:18:28 +0530
From:	Sachin Kamat <sachin.kamat@...aro.org>
To:	Nishanth Menon <nm@...com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Mark Brown <broonie@...nel.org>,
	Laxman Dewangan <ldewangan@...dia.com>, gg@...mlogic.co.uk,
	yong.shen@...aro.org, Sascha Hauer <s.hauer@...gutronix.de>,
	marek.vasut@...il.com, Nancy.Chen@...escale.com
Subject: Re: [PATCH 7/7] regulator: ti-abb: Use devm_regulator_register

On 4 September 2013 22:03, Nishanth Menon <nm@...com> wrote:
> On 09/04/2013 11:26 AM, Sachin Kamat wrote:

> I accept that probe failure gives me the required info for fail, and
> the cleanup of log prints also make sense, just that the log refactor
> seems out of context to the specific change.

As I mentioned earlier generally when you do these kind of
conversions, most of the trivial
clean-ups are also done along with it. Probably you would have
appreciated a mention about
this in the commit log too.

 --
With warm regards,
Sachin
--
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/