From: sentient@digitalfantasy.co.nz (Sentient)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: vt8500: clk: Add clock support for arch-vt8500
Date: Wed, 25 Jul 2012 21:40:09 +1200 [thread overview]
Message-ID: <000001cd6a49$7bb8d500$732a7f00$@digitalfantasy.co.nz> (raw)
In-Reply-To: <CAJOA=zNNE18DWwSgfh0H0zGgqpFhPeZrZ8zc0i_cxPBUc2VuoQ@mail.gmail.com>
Thanks Mike,
I might actually have a new patch up by then as the device tree support is coming along nicely.
Regards,
Tony
> -----Original Message-----
> From: vt8500-wm8505-linux-kernel at googlegroups.com [mailto:vt8500-wm8505-linux-kernel at googlegroups.com] On Behalf Of
> Turquette, Mike
> Sent: Wednesday, 25 July 2012 9:08 a.m.
> To: Tony Prisk
> Cc: VT8500 mailing list; linux-kernel at vger.kernel.org; linux-arm-kernel at lists.infradead.org; Russell King; Arnd Bergmann; Alexey
> Charkov
> Subject: Re: [PATCH] ARM: vt8500: clk: Add clock support for arch-vt8500
>
> On Sun, Jul 22, 2012 at 8:03 AM, Tony Prisk <linux@prisktech.co.nz> wrote:
> > This patch adds common clock framework support for arch-vt8500.
> > WM8650 support is included in preparation for devicetree support.
> > Each SoC has a seperate initialization function due to no
> > devicetree support to identify SoCs at the moment. Once devicetree
> > is implemented, VT8500 and WM8505 should be combined. WM8650 uses
> > different functions for clocks.
> >
> > Signed-off-by: Tony Prisk <linux@prisktech.co.nz>
>
> Hi Tony,
>
> I'll give this a more thorough review once the -rc1 window is over.
>
> Regards,
> Mike
prev parent reply other threads:[~2012-07-25 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 15:03 [PATCH] ARM: vt8500: clk: Add clock support for arch-vt8500 Tony Prisk
2012-07-24 19:25 ` Arnd Bergmann
2012-07-24 21:07 ` Turquette, Mike
2012-07-25 9:40 ` Sentient [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='000001cd6a49$7bb8d500$732a7f00$@digitalfantasy.co.nz' \
--to=sentient@digitalfantasy.co.nz \
--cc=linux-arm-kernel@lists.infradead.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).