From: Simon Horman <horms@verge.net.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-sh@vger.kernel.org, linux-serial@vger.kernel.org
Subject: Re: [PATCH 0/2] serial: sh-sci: Prepare for CCF migration
Date: Sat, 14 Dec 2013 10:00:45 +0900 [thread overview]
Message-ID: <20131214010045.GD12584@verge.net.au> (raw)
In-Reply-To: <20131203184346.GB23280@kroah.com>
On Tue, Dec 03, 2013 at 10:43:46AM -0800, Greg Kroah-Hartman wrote:
> On Mon, Dec 02, 2013 at 02:36:32PM +0100, Laurent Pinchart wrote:
> > Hi Greg,
> >
> > On Thursday 28 November 2013 18:11:44 Laurent Pinchart wrote:
> > > Hello,
> > >
> > > This patch set prepares the driver to CCF migration by replacing
> > > clk_enable() and clk_disable() by clk_prepare_enable() and
> > > clk_disable_unprepare() respectively (2/2). In order to do so it first
> > > ensures that the clk_enable() and clk_disable() calls will only take place
> > > from non-atomic context (1/2).
> > >
> > > Greg, these patches are dependencies for a bunch of ARM patches that will go
> > > through Simon's tree. Would you be fine if Simon merged all sh-sci patches
> > > through his tree for v3.14 ?
> >
> > Ping ?
>
> Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Thanks, I will (finally) queue these up.
prev parent reply other threads:[~2013-12-14 1:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-28 17:11 [PATCH 0/2] serial: sh-sci: Prepare for CCF migration Laurent Pinchart
2013-11-28 17:11 ` [PATCH 1/2] serial: sh-sci: Don't enable/disable port from within break timer Laurent Pinchart
2013-11-28 17:11 ` [PATCH 2/2] serial: sh-sci: Convert to clk_prepare/unprepare Laurent Pinchart
2013-11-29 2:15 ` [PATCH 0/2] serial: sh-sci: Prepare for CCF migration Magnus Damm
2013-12-02 13:36 ` Laurent Pinchart
2013-12-03 18:43 ` Greg Kroah-Hartman
2013-12-14 1:00 ` Simon Horman [this message]
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=20131214010045.GD12584@verge.net.au \
--to=horms@verge.net.au \
--cc=gregkh@linuxfoundation.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-serial@vger.kernel.org \
--cc=linux-sh@vger.kernel.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).