From: sameo@linux.intel.com (Samuel Ortiz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/8] clk: ux500: Fixup smp_twd clk for clk notifiers
Date: Sun, 28 Oct 2012 23:59:18 +0100 [thread overview]
Message-ID: <20121028225918.GC5411@sortiz-mobl> (raw)
In-Reply-To: <CAPDyKFof65xAVyOo3FrdS2uYQwB1Wq3553PKj04FR6JXaJsH6Q@mail.gmail.com>
Hi Ulf,
On Fri, Oct 26, 2012 at 10:19:24AM +0200, Ulf Hansson wrote:
> On 11 October 2012 17:19, Lee Jones <lee.jones@linaro.org> wrote:
> > On Thu, 11 Oct 2012, Linus Walleij wrote:
> >
> >> On Thu, Oct 11, 2012 at 3:44 PM, Lee Jones <lee.jones@linaro.org> wrote:
> >>
> >> >> Patches are based on Linus Torvalds tree with latest commit as of okt 10.
> >> >
> >> > Hmm... I get:
> >> >
> >> > Applying: clk: ux500: Support for prcmu_scalable_rate clock
> >> > error: drivers/clk/ux500/clk-prcmu.c: does not exist in index
> >> > error: drivers/clk/ux500/clk.h: does not exist in index
> >> > Patch failed at 0001 clk: ux500: Support for prcmu_scalable_rate clock
> >> >
> >> > So when did drivers/clk/ux500/* arrive?
> >>
> >> Exactly here, 10 days ago on Torvalds' master branch:
> >
> > Ah I see. Basing patches on commits half way through the merge
> > window. Good move! ;)
> >
> > --
> > Lee Jones
> > Linaro ST-Ericsson Landing Team Lead
> > Linaro.org ? Open source software for ARM SoCs
> > Follow Linaro: Facebook | Twitter | Blog
>
> Samuel, a kind reminder on this, trying to collect acks to be able to
> advise Mike to take this series through his clk tree. There are two
> mfd patches.
> [PATCH 2/8] mfd: db8500: Provide cpufreq table as platform data
> [PATCH 5/8] mfd: db8500: Connect ARMSS clk to ARM OPP
Sorry for the delay:
Acked-by: Samuel Ortiz <sameo@linux.intel.com>
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next prev parent reply other threads:[~2012-10-28 22:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-10 11:42 [PATCH 0/8] clk: ux500: Fixup smp_twd clk for clk notifiers Ulf Hansson
2012-10-10 11:42 ` [PATCH 1/8] ARM: ux500: Remove cpufreq platform device Ulf Hansson
2012-10-10 11:42 ` [PATCH 2/8] mfd: db8500: Provide cpufreq table as platform data Ulf Hansson
2012-10-10 11:42 ` [PATCH 3/8] cpufreq: db8500: Register as a platform driver Ulf Hansson
2012-10-10 11:42 ` [PATCH 4/8] cpufreq: db8500: Fetch cpufreq table from platform data Ulf Hansson
2012-10-11 13:41 ` Lee Jones
2012-10-11 15:49 ` Lee Jones
2012-10-10 11:42 ` [PATCH 5/8] mfd: db8500: Connect ARMSS clk to ARM OPP Ulf Hansson
2012-10-10 11:42 ` [PATCH 6/8] clk: ux500: Support for prcmu_scalable_rate clock Ulf Hansson
2012-10-10 11:42 ` [PATCH 7/8] clk: ux500: Add armss clk and fixup smp_twd clk for u8500 Ulf Hansson
2012-10-10 11:42 ` [PATCH 8/8] cpufreq: db8500: Use armss clk to update frequency Ulf Hansson
2012-10-26 8:10 ` Ulf Hansson
2012-10-26 11:20 ` Rafael J. Wysocki
2012-10-11 13:44 ` [PATCH 0/8] clk: ux500: Fixup smp_twd clk for clk notifiers Lee Jones
2012-10-11 14:24 ` Linus Walleij
2012-10-11 15:19 ` Lee Jones
2012-10-26 8:19 ` Ulf Hansson
2012-10-26 8:57 ` Linus Walleij
2012-10-26 18:03 ` Mike Turquette
2012-10-26 23:34 ` Linus Walleij
2012-10-28 22:59 ` Samuel Ortiz [this message]
2012-11-05 12:33 ` Ulf Hansson
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=20121028225918.GC5411@sortiz-mobl \
--to=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).