From: mturquette@ti.com (Mike Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 0/4] clk: Convert ARM ux500 to common clock
Date: Thu, 06 Sep 2012 16:25:17 -0700 [thread overview]
Message-ID: <20120906232517.20289.46469@nucleus> (raw)
In-Reply-To: <CACRpkdbH-vCfAYavO4Ef78Dy1dnphXc+JD76YHAhOiORsCWFHA@mail.gmail.com>
Quoting Linus Walleij (2012-08-27 17:02:53)
> On Mon, Aug 27, 2012 at 6:45 AM, Ulf Hansson <ulf.hansson@stericsson.com> wrote:
>
> > This converts the ux500 machine specific clocks to the common
> > clock framework. Old clock code are then removed from the ux500
> > machine directory.
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> For this whole patch set, Mike when you're pleased with the looks of this I'd
> be very happy if you could merge this to your tree for some rotation
> in linux-next....
>
I've pulled it into clk-next. Predictably ux500_defconfig breaks since
cpu_is_u8540 does not exist in my code. Merging clk-next onto latest
linux-next shows that everything builds nicely (well the are some
warnings but nothing dire...).
Regards,
Mike
> Yours,
> Linus Walleij
next prev parent reply other threads:[~2012-09-06 23:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 13:45 [PATCH V2 0/4] clk: Convert ARM ux500 to common clock Ulf Hansson
2012-08-27 13:45 ` [PATCH V2 1/4] clk: ux500: Adapt PRCMU and PRCC clocks for common clk Ulf Hansson
2012-08-27 13:45 ` [PATCH V2 2/4] clk: ux500: First version of clock definitions for ux500 Ulf Hansson
2012-08-27 13:45 ` [PATCH V2 3/4] clk: ux500: Clock definitions for u8500 Ulf Hansson
2012-08-27 13:45 ` [PATCH V2 4/4] ARM: ux500: Switch to use common clock framework Ulf Hansson
2012-08-28 0:02 ` [PATCH V2 0/4] clk: Convert ARM ux500 to common clock Linus Walleij
2012-09-06 23:25 ` Mike Turquette [this message]
2012-09-07 8:05 ` Linus Walleij
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=20120906232517.20289.46469@nucleus \
--to=mturquette@ti.com \
--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