From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v7 0/6] sh73a0 common clock framework implementation
Date: Fri, 19 Dec 2014 09:14:28 +0000 [thread overview]
Message-ID: <20141219091425.GA9634@verge.net.au> (raw)
In-Reply-To: <1418222727-19888-1-git-send-email-ulrich.hecht+renesas@gmail.com>
On Fri, Dec 19, 2014 at 09:04:44AM +0100, Geert Uytterhoeven wrote:
> On Fri, Dec 19, 2014 at 12:48 AM, Simon Horman <horms@verge.net.au> wrote:
> >> > As Mike has acked the first patch I would like to take the entire series
> >> > through my tree.
> >>
> >> OK... Less work for me ;-)
> >
> > :)
> >
> >> Will you also take the other clock related patches floating around?
> >> E.g. "[PATCH v2] clk: shmobile: div6: Avoid changing divisor in .disable()",
> >> and a few other adding support for more R-Car Gen2 SoCs?
> >
> > As Mike has indicated he will take them I do not plan to.
>
> The above mentioned div6 patch is not the div6 patch in clk/for-next.
> This is a new one.
Thanks, I see that now.
I'm happy to take this if it is a dependency for other mach-shmobile
patches for v3.20. But it would need Mike's Ack.
next prev parent reply other threads:[~2014-12-19 9:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 14:45 [PATCH v7 0/6] sh73a0 common clock framework implementation Ulrich Hecht
2014-12-17 7:54 ` Magnus Damm
2014-12-17 8:01 ` Geert Uytterhoeven
2014-12-17 8:40 ` Magnus Damm
2014-12-17 8:54 ` Geert Uytterhoeven
2014-12-17 11:39 ` Laurent Pinchart
2014-12-18 3:01 ` Simon Horman
2014-12-18 8:09 ` Geert Uytterhoeven
2014-12-18 8:16 ` Geert Uytterhoeven
2014-12-18 23:48 ` Simon Horman
2014-12-19 0:53 ` Simon Horman
2014-12-19 8:04 ` Geert Uytterhoeven
2014-12-19 9:14 ` Simon Horman [this message]
2014-12-21 9:04 ` Geert Uytterhoeven
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=20141219091425.GA9634@verge.net.au \
--to=horms@verge.net.au \
--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