From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ARM: shmobile: Remove ARCH_SHMOBILE_MULTI
Date: Thu, 9 Feb 2017 14:40:21 +0100 [thread overview]
Message-ID: <20170209134020.GA20339@verge.net.au> (raw)
In-Reply-To: <SG2PR06MB1165BBFDAA507BB95DF0A2808A450@SG2PR06MB1165.apcprd06.prod.outlook.com>
On Thu, Feb 09, 2017 at 01:12:24PM +0000, Chris Brandt wrote:
> Hi Simon and Geert,
>
> On Thursday, February 09, 2017, Simon Horman wrote:
> > On Thu, Feb 09, 2017 at 11:18:47AM +0100, Geert Uytterhoeven wrote:
> > > Hi Simon, Magnus,
> > >
> > > This patch series completes the migration from ARCH_SHMOBILE_MULTI to
> > > ARCH_RENESAS, which was started by commit 9b5ba0df4ea4 ("ARM: shmobile:
> > > Introduce ARCH_RENESAS").
> > >
> > > Thanks for applying!
> >
> > Thanks, nice to see this coming to an end.
> >
> > I have queued up patch 1/2 in the dt-for-v4.12 branch.
> >
> > I am of a mind to defer patch 2/2 because it looks like it should go in
> > the soc-for-v4.12 branch and I'd rather not add a dependency on the dt-
> > for-v4.12 branch for a cleanup.
> >
> > In a perfect world we could have one branch to rule them all; we do not
> > live in that world.
>
>
> Out of curiosity, when will arch/arm/mach-shmobile and arch/arm/configs/shmobile_defconfig be renamed (if ever)??
There are no plans at this time.
I am happy to discuss a rename if there is a need for it.
prev parent reply other threads:[~2017-02-09 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 10:18 [PATCH 0/2] ARM: shmobile: Remove ARCH_SHMOBILE_MULTI Geert Uytterhoeven
2017-02-09 10:18 ` [PATCH 1/2] ARM: dts: renesas: Switch from ARCH_SHMOBILE_MULTI to ARCH_RENESAS Geert Uytterhoeven
2017-02-09 10:18 ` [PATCH 2/2] ARM: shmobile: Remove ARCH_SHMOBILE_MULTI Geert Uytterhoeven
2017-02-09 10:55 ` [PATCH 0/2] " Simon Horman
2017-02-09 13:12 ` Chris Brandt
2017-02-09 13:40 ` 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=20170209134020.GA20339@verge.net.au \
--to=horms@verge.net.au \
--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).