From: Stephen Boyd <sboyd@codeaurora.org>
To: Olof Johansson <olof@lixom.net>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
"arm@kernel.org" <arm@kernel.org>,
linux-clk@vger.kernel.org
Subject: Re: [PATCH 2/3] clk/ARM: move Ux500 PRCC bases to the device tree
Date: Thu, 13 Aug 2015 11:29:12 -0700 [thread overview]
Message-ID: <20150813182814.GR26614@codeaurora.org> (raw)
In-Reply-To: <20150813122831.GC23581@localhost>
On 08/13, Olof Johansson wrote:
> On Wed, Aug 12, 2015 at 02:02:50PM +0200, Linus Walleij wrote:
> > On Thu, Jul 30, 2015 at 3:19 PM, Linus Walleij <linus.walleij@linaro.org> wrote:
> >
> > > The base addresses for the Ux500 PRCC controllers are hardcoded,
> > > let's move them to the clock node in the device tree and delete
> > > the constants.
> > >
> > > Cc: Ulf Hansson <ulf.hansson@linaro.org>
> > > Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> > > ---
> > > Ulf/Mike: please ACK this so I can take it through ARM SoC.
> >
> > It appears this needs to go through the clk tree with the rest
> > (1/3, 3/3).
> >
> > Can I have an ACK from the ARM SoC people so they know
> > this is happening?
>
> Acked-by: Olof Johansson <olof@lixom.net>
>
> I'm assuming you'll keep track of/avoid conflicts yourself, so I didn't
> double-check for it.
>
Thanks. Applied to clk-next.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2015-08-13 18:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 13:19 [PATCH 2/3] clk/ARM: move Ux500 PRCC bases to the device tree Linus Walleij
2015-08-11 23:35 ` Michael Turquette
2015-08-12 12:02 ` Linus Walleij
2015-08-13 12:28 ` Olof Johansson
2015-08-13 18:29 ` Stephen Boyd [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=20150813182814.GR26614@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=olof@lixom.net \
--cc=ulf.hansson@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.