From: Wolfram Sang <w.sang@pengutronix.de>
To: Viresh Kumar <viresh.kumar@st.com>
Cc: ben-linux@fluff.org, spear-devel@list.st.com,
viresh.linux@gmail.com, khali@linux-fr.org,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] i2c: designware: Add clk_{un}prepare() support
Date: Sun, 22 Apr 2012 19:26:11 +0200 [thread overview]
Message-ID: <20120422172611.GA15041@pengutronix.de> (raw)
In-Reply-To: <b562073871c8c3c13a1f59698f69cfdf65db3b5a.1334662366.git.viresh.kumar@st.com>
[-- Attachment #1: Type: text/plain, Size: 566 bytes --]
On Tue, Apr 17, 2012 at 05:04:31PM +0530, Viresh Kumar wrote:
> clk_{un}prepare is mandatory for platforms using common clock framework. Since
> this driver is used by SPEAr platform, which supports common clock framework,
> add clk_{un}prepare() support for designware i2c.
>
> Signed-off-by: Viresh Kumar <viresh.kumar@st.com>
? Can't apply, which version is this against? Looks good otherwise.
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-22 17:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 8:53 [PATCH] i2c: designware: Add clk_{un}prepare() support Viresh Kumar
[not found] ` <caa4a0645f80f199b31ec16de37a5c4c9c67a6fa.1334652570.git.viresh.kumar-qxv4g6HH51o@public.gmane.org>
2012-04-17 11:34 ` [PATCH V2] " Viresh Kumar
2012-04-22 17:26 ` Wolfram Sang [this message]
2012-04-22 17:38 ` viresh kumar
[not found] ` <CAOh2x=mHS9h6kHxw2of-XWTtv35-SHRRno9Jdkb_3HuDoAovAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-22 18:38 ` Wolfram Sang
[not found] ` <20120422183806.GB24810-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-04-24 3:31 ` Viresh Kumar
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=20120422172611.GA15041@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=ben-linux@fluff.org \
--cc=khali@linux-fr.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=spear-devel@list.st.com \
--cc=viresh.kumar@st.com \
--cc=viresh.linux@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).