From: Simon Horman <horms@verge.net.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] bus: simple-pm-bus: Use ARCH_RENESAS
Date: Tue, 8 Mar 2016 09:29:53 +0900 [thread overview]
Message-ID: <20160308002953.GF5024@verge.net.au> (raw)
In-Reply-To: <CAMuHMdVjpYg1q_ZGm7tVASvrAE8oEzVZFTtua4LVDFsY7cHCVA@mail.gmail.com>
On Mon, Mar 07, 2016 at 02:22:57PM +0100, Geert Uytterhoeven wrote:
> On Fri, Mar 4, 2016 at 6:20 AM, Simon Horman <horms@verge.net.au> wrote:
> > On Thu, Mar 03, 2016 at 09:31:49AM +0100, Geert Uytterhoeven wrote:
> >> On Thu, Mar 3, 2016 at 2:39 AM, Simon Horman <horms+renesas@verge.net.au> wrote:
> >> > Make use of ARCH_RENESAS in place of ARCH_SHMOBILE.
> >> >
> >> > 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>
> >
> > I'm a little unsure of who should take this but for now I will
> > queue it up in next with a view to sending a pull request to Linus
> > for v4.6. I'm open to other ideas.
>
> All but two entries in drivers/bus/Kconfig are for ARM platforms (the
> other two are for MIPS platforms), so I think arm-soc is appropriate.
>
> Alternatively, GregKH?
Point taken. I'll queue it up for v4.7 for arm-soc.
prev parent reply other threads:[~2016-03-08 0:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 1:39 [PATCH] bus: simple-pm-bus: Use ARCH_RENESAS Simon Horman
2016-03-03 8:31 ` Geert Uytterhoeven
2016-03-04 5:20 ` Simon Horman
2016-03-07 13:22 ` Geert Uytterhoeven
2016-03-08 0:29 ` Simon Horman [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=20160308002953.GF5024@verge.net.au \
--to=horms@verge.net.au \
--cc=geert@linux-m68k.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.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 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).