From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/6 v2] ARM: shmobile: r8a73a4: detailed clock topology support
Date: Fri, 12 Apr 2013 06:58:04 +0000 [thread overview]
Message-ID: <20130412065803.GB27274@verge.net.au> (raw)
In-Reply-To: <87r4ipk3rp.wl%kuninori.morimoto.gx@renesas.com>
On Thu, Apr 11, 2013 at 10:10:02PM -0700, Kuninori Morimoto wrote:
>
> Hi Magnus
>
> > > Hi Simon, Magnus
> > >
> > > These patches are v2 of r8a73a4 clock topology support.
> > >
> > > These are tested on APE6EVM board,
> > > and based on renesas-next-20130404v2 tags
> > >
> > > Kuninori Morimoto (5):
> > > ARM: shmobile: r8a73a4: add main clock
> > > ARM: shmobile: r8a73a4: add pll clocks
> > > ARM: shmobile: r8a73a4: add div4 clocks
> > > ARM: shmobile: r8a73a4: add div6 clocks
> > > ARM: shmobile: ape6evm: MP clock parent become EXTAL2
> > >
> > > arch/arm/mach-shmobile/board-ape6evm.c | 15 ++
> > > arch/arm/mach-shmobile/clock-r8a73a4.c | 375 ++++++++++++++++++++++++++++++--
> >
> > Magnus, could you review these patches?
>
> ping ?
pong
I have spoken with Magnus and queued-up the patches for v3.11.
The first 4 patches are in the soc-r8a77a3 branch.
I have merged that branch into the boards-ape6evm branch
and queued-up the last patch of the series there.
next prev parent reply other threads:[~2013-04-12 6:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 4:19 [PATCH 0/6 v2] ARM: shmobile: r8a73a4: detailed clock topology support Kuninori Morimoto
2013-04-09 12:50 ` Simon Horman
2013-04-12 5:10 ` Kuninori Morimoto
2013-04-12 6:58 ` Simon Horman [this message]
2013-04-12 7:16 ` Kuninori Morimoto
2013-04-12 7:22 ` Simon Horman
2013-04-12 7:39 ` Kuninori Morimoto
2013-04-12 9:00 ` Simon Horman
2013-04-12 10:47 ` Kuninori Morimoto
2013-04-15 3:52 ` Simon Horman
2013-04-16 3:11 ` Simon Horman
2013-04-16 3:13 ` Kuninori Morimoto
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=20130412065803.GB27274@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