From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-sh@vger.kernel.org, Mike Turquette <mturquette@linaro.org>,
Chris Ball <cjb@laptop.org>,
Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>,
linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: [PATCH 07/12] mmc: sh_mmcif: Convert to clk_prepare/unprepare
Date: Thu, 31 Oct 2013 00:48:47 +0100 [thread overview]
Message-ID: <14289582.5zfRMUTTcX@avalon> (raw)
In-Reply-To: <CAPDyKFoNn9g2RmGvFnmDYfiOhZHQYY33zA=Rk5DQWEBNDyhfHQ@mail.gmail.com>
Hi Uluf,
On Thursday 31 October 2013 00:27:23 Ulf Hansson wrote:
> On 31 October 2013 00:13, Laurent Pinchart wrote:
> > On Wednesday 30 October 2013 23:23:37 Guennadi Liakhovetski wrote:
> >> On Tue, 29 Oct 2013, Guennadi Liakhovetski wrote:
> >> > On Mon, 28 Oct 2013, Laurent Pinchart wrote:
> >> > > Turn clk_enable() and clk_disable() calls into clk_prepare_enable()
> >> > > and clk_disable_unprepare() to get ready for the migration to the
> >> > > common clock framework.
> >> > >
> >> > > Cc: Chris Ball <cjb@laptop.org>
> >> > > Cc: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
> >> > > Cc: linux-mmc@vger.kernel.org
> >> > > Signed-off-by: Laurent Pinchart
> >> > > <laurent.pinchart+renesas@ideasonboard.com>
> >> >
> >> > Acked-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
> >>
> >> Sorry, I just realised, that an identical patch
> >>
> >> http://patches.linaro.org/21212/
> >>
> >> has been submitted prior to this one, so, we should really take the other
> >> one.
> >
> > I'm fine with that, as long as one of the two patches hit mainline as soon
> > as possible.
>
> I can put together a new pull request for Chris asap, but in the end
> it will be his call to take it now or later.
That would be great. It can wait for v3.14 though, but having the patch in
v3.13 would be nice.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-10-30 23:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-28 22:49 [PATCH 00/12] Prepare various SH/R Mobile/Car drivers for CCF migration Laurent Pinchart
2013-10-28 22:49 ` [PATCH 07/12] mmc: sh_mmcif: Convert to clk_prepare/unprepare Laurent Pinchart
2013-10-29 8:10 ` Guennadi Liakhovetski
2013-10-30 22:23 ` Guennadi Liakhovetski
2013-10-30 23:13 ` Laurent Pinchart
2013-10-30 23:27 ` Ulf Hansson
2013-10-30 23:48 ` Laurent Pinchart [this message]
2013-10-28 22:49 ` [PATCH 08/12] mmc: sh_mobile_sdhi: " Laurent Pinchart
2013-10-29 8:09 ` Guennadi Liakhovetski
2013-11-09 12:56 ` Laurent Pinchart
2013-11-26 2:02 ` Laurent Pinchart
2013-12-11 12:01 ` Laurent Pinchart
2013-12-12 1:29 ` Chris Ball
2013-12-12 2:16 ` Laurent Pinchart
2013-12-12 2:25 ` Chris Ball
2013-12-14 1:05 ` Simon Horman
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=14289582.5zfRMUTTcX@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=cjb@laptop.org \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=g.liakhovetski@gmx.de \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mturquette@linaro.org \
--cc=ulf.hansson@linaro.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 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).