public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Olof Johansson <olof@lixom.net>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Alexandre Belloni <alexandre.belloni@free-electrons.com>,
	ARM Maintainers <arm@kernel.org>,
	Boris BREZILLON <boris.brezillon@free-electrons.com>,
	Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: re-fromat AT91 part to match other entries
Date: Mon, 26 Jan 2015 18:13:44 -0800	[thread overview]
Message-ID: <20150127021344.GA22154@quad.lixom.net> (raw)
In-Reply-To: <54C660FE.3000401@atmel.com>

On Mon, Jan 26, 2015 at 04:45:02PM +0100, Nicolas Ferre wrote:
> Le 14/01/2015 10:05, Arnd Bergmann a écrit :
> > On Wednesday 14 January 2015 00:47:59 Alexandre Belloni wrote:
> >>
> >> On 13/01/2015 at 15:09:56 -0800, Olof Johansson wrote :
> >>> On Tue, Jan 13, 2015 at 03:43:00PM +0100, Nicolas Ferre wrote:
> >>>> The entries are separated as ARM V4/V5 and ARM V7 as some other per-SoC config
> >>>> options may be removed in the near future.
> >>>>
> >>>> Signed-off-by: Nicolas Ferre <nicolas.ferre@atmel.com>
> >>>> ---
> >>>> Hi Olof,
> >>>>
> >>>> This is an attempt to match other ARM SoC families format.
> >>>> If you feel that the patch can be good, do not hesitate to take it yourself. I
> >>>> don't plan to integrate it in any of my pull-request so it can appear quickly in
> >>>> arm-soc and can be used by everyone.
> >>>
> >>> Hi,
> >>>
> >>> If you see what Peter did, he split up the rules per-SoC based on how
> >>> things were selectable in Kconfig. Since you seem to have the Kconfig
> >>> entries already, how about doing the same? That way the same information
> >>> w.r.t. SoC family that you have as comments isn't lost either.
> >>>
> >>
> >> You didn't see the patch set yet because it depends on a lot of other
> >> series still being discussed but after the switch to multiplatform, the
> >> only config option left will be SOC_AT91RM9200, SOC_AT91SAM9 (both
> >> under SOC_SAM_V4_V5) and SOC_SAMA5, under SOC_SAM_V7.
> >>
> >> That's our plan, unless you feel that we should keep one config option
> >> per SoC.
> > 
> > With the patches that I prepared last year, all of AT91SAM9 becomes
> > one small file, so there really isn't any need to have separate Kconfig
> > options.
> 
> Hi Olof,
> 
> After what noted Alexandre and Arnd, don't you think my initial attempt
> was okay? Aka: ping ;-)

Ah, yes. Applied now.


-Olof

      reply	other threads:[~2015-01-27  2:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20150112224203.GL22090@quad.lixom.net>
2015-01-13 14:43 ` [PATCH] ARM: dts: re-fromat AT91 part to match other entries Nicolas Ferre
2015-01-13 23:09   ` Olof Johansson
2015-01-13 23:47     ` Alexandre Belloni
2015-01-14  9:05       ` Arnd Bergmann
2015-01-26 15:45         ` Nicolas Ferre
2015-01-27  2:13           ` Olof Johansson [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=20150127021344.GA22154@quad.lixom.net \
    --to=olof@lixom.net \
    --cc=alexandre.belloni@free-electrons.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=boris.brezillon@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nicolas.ferre@atmel.com \
    --cc=plagnioj@jcrosoft.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