From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Laxman Dewangan <ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Cc: khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org,
swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] i2c: tegra: use clk_disable_unprepare in place of clk_disable
Date: Wed, 20 Jun 2012 10:27:02 -0600 [thread overview]
Message-ID: <4FE1F9D6.6090802@wwwdotorg.org> (raw)
In-Reply-To: <4FE1F9A0.6080200-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
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.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: khali@linux-fr.org, w.sang@pengutronix.de, swarren@nvidia.com,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
pgaikwad@nvidia.com
Subject: Re: [PATCH] i2c: tegra: use clk_disable_unprepare in place of clk_disable
Date: Wed, 20 Jun 2012 10:27:02 -0600 [thread overview]
Message-ID: <4FE1F9D6.6090802@wwwdotorg.org> (raw)
In-Reply-To: <4FE1F9A0.6080200@wwwdotorg.org>
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.
next prev parent reply other threads:[~2012-06-20 16:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 12:56 [PATCH] i2c: tegra: use clk_disable_unprepare in place of clk_disable Laxman Dewangan
2012-06-20 12:56 ` Laxman Dewangan
[not found] ` <1340196960-3002-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-20 16:26 ` Stephen Warren
2012-06-20 16:26 ` Stephen Warren
[not found] ` <4FE1F9A0.6080200-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-20 16:27 ` Stephen Warren [this message]
2012-06-20 16:27 ` Stephen Warren
2012-06-25 9:46 ` Laxman Dewangan
[not found] ` <4FE83374.6090608-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-25 15:55 ` Stephen Warren
2012-06-25 15:55 ` Stephen Warren
[not found] ` <4FE889D6.4030500-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2012-06-26 6:27 ` Laxman Dewangan
2012-06-26 6:27 ` Laxman Dewangan
[not found] ` <4FE9564C.4010502-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2012-06-26 16:28 ` Stephen Warren
2012-06-26 16:28 ` Stephen Warren
2012-06-27 15:59 ` Laxman Dewangan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FE1F9D6.6090802@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
--cc=ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=pgaikwad-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org \
--cc=w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.