SUPERH platform development
 help / color / mirror / Atom feed
From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 03/05] ARM: shmobile: sh73a0: Add Multiplatform support
Date: Tue, 23 Dec 2014 00:15:06 +0000	[thread overview]
Message-ID: <20141223001506.GC2817@verge.net.au> (raw)
In-Reply-To: <20141217094234.7039.79623.sendpatchset@w520>

On Tue, Dec 23, 2014 at 09:12:34AM +0900, Simon Horman wrote:
> On Mon, Dec 22, 2014 at 11:10:26AM +0100, Geert Uytterhoeven wrote:
> > On Wed, Dec 17, 2014 at 10:42 AM, Magnus Damm <magnus.damm@gmail.com> wrote:
> > >
> > > --- 0001/arch/arm/mach-shmobile/Kconfig
> > > +++ work/arch/arm/mach-shmobile/Kconfig 2014-12-16 19:11:36.000000000 +0900
> > > @@ -52,6 +52,11 @@ config ARCH_R7S72100
> > >         bool "RZ/A1H (R7S72100)"
> > >         select SYS_SUPPORTS_SH_MTU2
> > >
> > > +config ARCH_SH73A0
> > > +       bool "SH-Mobile AG5 (R8A73A00)"
> > > +       select ARCH_RMOBILE
> > > +       select RENESAS_INTC_IRQPIN
> > > +
> > >  config ARCH_R8A7740
> > >         bool "R-Mobile A1 (R8A77400)"
> > >         select ARCH_RMOBILE
> > 
> > Shall we keep this sorted?
> > That does mean the entries for the old SH73xx are at the end of the
> > list, though.
> 
> Sorting it is nice. But are other entries out of order?
> In either case, feel free to submit a cleanup.

Sorry, for some reason I thought I had queued up the above patch.

I think sorting makes sense. And it looks like the other entries are already
sorted. So adjusting this patch seems like a good idea to me. But I'll
let Magnus decide.

      parent reply	other threads:[~2014-12-23  0:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-17  9:42 [PATCH v2 03/05] ARM: shmobile: sh73a0: Add Multiplatform support Magnus Damm
2014-12-17 13:49 ` Geert Uytterhoeven
2014-12-17 14:17 ` Magnus Damm
2014-12-17 14:24 ` Geert Uytterhoeven
2014-12-22 10:10 ` Geert Uytterhoeven
2014-12-23  0:12 ` Simon Horman
2014-12-23  0:15 ` 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=20141223001506.GC2817@verge.net.au \
    --to=horms@verge.net.au \
    --cc=linux-sh@vger.kernel.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