From: Stephen Boyd <sboyd@codeaurora.org>
To: Simon Horman <horms@verge.net.au>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Michael Turquette <mturquette@baylibre.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
linux-clk <linux-clk@vger.kernel.org>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] clk: shmobile: Remove ARCH_SHMOBILE_MULTI
Date: Thu, 25 Feb 2016 15:44:34 -0800 [thread overview]
Message-ID: <20160225234434.GM28849@codeaurora.org> (raw)
In-Reply-To: <20160223091000.GA18694@verge.net.au>
On 02/23, Simon Horman wrote:
> On Tue, Feb 23, 2016 at 09:19:27AM +0100, Geert Uytterhoeven wrote:
> > CC The New Mike ;-)
> >
> > On Tue, Feb 23, 2016 at 1:57 AM, Simon Horman
> > <horms+renesas@verge.net.au> wrote:
> > > As of 9b5ba0df4ea4 ("ARM: shmobile: Introduce ARCH_RENESAS") all platforms
> > > that use Renesas clock drivers now select ARCH_RENESAS. As it is present in
> > > drivers/clk/Makefile ARCH_SHMOBILE_MULTI may now be removed.
> > >
> > > This is part of an ongoing process to migrate from ARCH_SHMOBILE to
> > > ARCH_RENESAS the motivation for which being that RENESAS seems to be a more
> > > appropriate name than SHMOBILE for the majority of Renesas ARM based SoCs.
> > >
> > > Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
> >
> > Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >
Applied to clk-next
> > > drivers/clk/Makefile | 1 -
> > > 1 file changed, 1 deletion(-)
> > >
> > > Based on clk-next
> > >
> > > diff --git a/drivers/clk/Makefile b/drivers/clk/Makefile
> > > index bae4be6501df..b19af449d2f3 100644
> > > --- a/drivers/clk/Makefile
> > > +++ b/drivers/clk/Makefile
> > > @@ -70,7 +70,6 @@ obj-$(CONFIG_COMMON_CLK_PXA) += pxa/
> > > obj-$(CONFIG_COMMON_CLK_QCOM) += qcom/
> > > obj-$(CONFIG_ARCH_ROCKCHIP) += rockchip/
> > > obj-$(CONFIG_COMMON_CLK_SAMSUNG) += samsung/
> > > -obj-$(CONFIG_ARCH_SHMOBILE_MULTI) += shmobile/
> >
> > Should we rename clk/shmobile/ to clk/renesas/?
> > Or is that too much of a hassle?
>
> I think it is a good idea. And I suspect it shouldn't be too difficult if
> we coordinate things with Mike to handle any in-flight patches for that
> directory.
Feel free to send the patch.
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-02-25 23:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 0:57 [PATCH] clk: shmobile: Remove ARCH_SHMOBILE_MULTI Simon Horman
2016-02-23 8:17 ` Geert Uytterhoeven
2016-02-23 8:19 ` Geert Uytterhoeven
2016-02-23 9:10 ` Simon Horman
2016-02-25 23:44 ` Stephen Boyd [this message]
2016-03-03 5:02 ` Simon Horman
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=20160225234434.GM28849@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-clk@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mturquette@baylibre.com \
/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.