From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: Rename ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY
Date: Tue, 12 Nov 2013 14:21:04 +0100 [thread overview]
Message-ID: <17979814.3ftdsWAt7J@avalon> (raw)
In-Reply-To: <20131112052625.GC28649@verge.net.au>
Hi Simon,
On Tuesday 12 November 2013 14:26:25 Simon Horman wrote:
> On Tue, Nov 12, 2013 at 02:11:37PM +0900, Simon Horman wrote:
> > On Sat, Nov 09, 2013 at 01:33:48PM +0100, Laurent Pinchart wrote:
> > > SH-Mobile platforms are transitioning from non-multiplatform to
> > > multiplatform kernel. A new ARCH_SHMOBILE_MULTI configuration symbol has
> > > been created to group all multiplatform-enabled SH-Mobile SoCs. The
> > > existing ARCH_SHMOBILE configuration symbol groups SoCs that haven't
> > > been converted yet.
> > >
> > > This arrangement works fine for the arch/ code, but lots of drivers
> > > needed on both ARCH_SHMOBILE and ARCH_SHMOBILE_MULTI depend on
> > > ARCH_SHMOBILE only. In order to avoid changing them, rename
> > > ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY, and create a new boolean
> > > ARCH_SHMOBILE configuration symbol that is selected by both
> > > ARCH_SHMOBILE_LEGACY and ARCH_SHMOBILE_MULTI.
> > >
> > > Signed-off-by: Laurent Pinchart
> > > <laurent.pinchart+renesas@ideasonboard.com>
> > > Acked-by: Magnus Damm <damm@opensource.se>
> >
> > Thanks, I have queued this up.
>
> I have dropped this for now as it seems that all of the
> shmobile defconfigs now need to be updated to use ARCH_SHMOBILE_LEGACY
> instead of ARCH_SHMOBILE.
Indeed, I forgot about that.
> It seems to me that needs to be part of this patch to avoid
> breaking bisecatability. Any thoughts?
The only bisection this would break is the defconfig bisection. I'm not sure
whether we need to care about that, Would that be a bit issue ? I'll submit a
separate patch, please feel free to squash it with this one if you believe it
should be.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-11-12 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-09 12:33 [PATCH 0/2] ARM: Rename ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY Laurent Pinchart
2013-11-09 12:33 ` [PATCH 1/2] " Laurent Pinchart
2013-11-12 5:11 ` Simon Horman
2013-11-12 5:26 ` Simon Horman
2013-11-12 13:21 ` Laurent Pinchart [this message]
2013-11-13 0:53 ` Simon Horman
2013-11-13 0:57 ` Laurent Pinchart
2013-11-19 1:45 ` Simon Horman
2013-11-19 1:53 ` Laurent Pinchart
2013-11-19 2:36 ` Simon Horman
2013-11-09 12:33 ` [PATCH 2/2] ASoC: sh: rcar: Depend on ARCH_SHMOBILE_LEGACY Laurent Pinchart
2013-12-06 10:07 ` Laurent Pinchart
2013-12-09 0:16 ` [alsa-devel] " Kuninori Morimoto
2013-12-09 12:57 ` Laurent Pinchart
2013-11-12 13:29 ` [PATCH 3/2] ARM: Rename ARCH_SHMOBILE to ARCH_SHMOBILE_LEGACY in defconfig Laurent Pinchart
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=17979814.3ftdsWAt7J@avalon \
--to=laurent.pinchart@ideasonboard.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).