linux-kernel - Re: [PATCH] i2c: tegra: use clk_disable_unprepare in place of clk

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:	Mon, 25 Jun 2012 15:16:28 +0530
From:	Laxman Dewangan <ldewangan@...dia.com>
To:	Stephen Warren <swarren@...dotorg.org>
CC:	"khali@...ux-fr.org" <khali@...ux-fr.org>,
	"w.sang@...gutronix.de" <w.sang@...gutronix.de>,
	Stephen Warren <swarren@...dia.com>,
	"linux-i2c@...r.kernel.org" <linux-i2c@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Prashant Gaikwad <pgaikwad@...dia.com>
Subject: Re: [PATCH] i2c: tegra: use clk_disable_unprepare in place of clk_disable

Stephen,

On Wednesday 20 June 2012 09:57 PM, Stephen Warren wrote:
> On 06/20/2012 10:26 AM, Stephen Warren wrote:
>> On 06/20/2012 06:56 AM, Laxman Dewangan wrote:
>>> Use clk_disable_unprepare() inplace of clk_disable().
>>> This was missed as part of moving clock enable/disable to
>>> prepare/unprepare for using the common clock framework.
> ...
>> I see no reason not to take the second patch in the series through the
>> I2C tree though.
> Uggh. Ignore that paragraph - the other patch was sent separately not as
> a series.

so are you taking care of this patch or do I need to send the patch 
based on your tree in place of linux-next?

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