From: Ludovic Desroches <ludovic.desroches@atmel.com>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <cyrille.pitchen@atmel.com>,
<plagnioj@jcrosoft.com>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/3] ARM: at91/defconfig: update sama5 defconfig
Date: Fri, 16 Oct 2015 08:44:00 +0200 [thread overview]
Message-ID: <20151016064400.GH26893@odux.rfo.atmel.com> (raw)
In-Reply-To: <561FC97D.2040806@atmel.com>
On Thu, Oct 15, 2015 at 05:42:53PM +0200, Nicolas Ferre wrote:
> Le 15/10/2015 17:31, Ludovic Desroches a écrit :
> > On Thu, Oct 15, 2015 at 03:24:51PM +0200, Alexandre Belloni wrote:
> >> Hi,
> >>
> >> On 14/10/2015 at 14:11:24 +0200, Ludovic Desroches wrote :
> >>> Add SAMA5D2 SoC plus Atmel flexcom and Atmel sdhci devices.
> >>>
> >>> Signed-off-by: Ludovic Desroches <ludovic.desroches@atmel.com>
> >>> ---
> >>> arch/arm/configs/sama5_defconfig | 6 +++++-
> >>> 1 file changed, 5 insertions(+), 1 deletion(-)
> >>>
> >> It is probably worth updating the multi_v7_defconfig too (in a separate
> >> patch).
> >>
> >
> > Maybe I have to send a whole defconfig update . I mean when you do
> > savedefconfig, you have more changes. I won't send each one separately. I
> > have kept changes which were in relation with the stuff I had.
> >
> > Or I can send a defconfig update from the savedefconfig and then add
> > sama5d2, flexcom and sdhci.
>
> Actually you can do this for our own AT91 defconfigs.
>
> For the multi_v7_defconfig I would recommend to simply make a patch with
> our updates and let the arm-soc maintainer merge it with their current
> one: I mean, they will manage the conflicts on this file anyway and the
> changes to this file will not be part of one or our pull-requests but a
> patch that they will handle separately: so no need to add more update
> than the strictly needed ones on our end.
>
In fact, I realize that I have read too quickly Alexandre's answer. I
have understood that I should put CONFIG_SOC_SAM_V7=y in a separate
patch.
So yes I would do a whole update for our defconfigs and only the
addition needed for the multi_v7 one
Ludovic
prev parent reply other threads:[~2015-10-16 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-14 12:11 [PATCH 1/3] ARM: at91/dt: sama5d2: add missing devices Ludovic Desroches
2015-10-14 12:11 ` [PATCH 2/3] ARM: at91/dt: sama5d2 Xplained: add several devices Ludovic Desroches
2015-10-14 12:11 ` [PATCH 3/3] ARM: at91/defconfig: update sama5 defconfig Ludovic Desroches
2015-10-15 13:24 ` Alexandre Belloni
2015-10-15 15:31 ` Ludovic Desroches
2015-10-15 15:42 ` Nicolas Ferre
2015-10-16 6:44 ` Ludovic Desroches [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=20151016064400.GH26893@odux.rfo.atmel.com \
--to=ludovic.desroches@atmel.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=cyrille.pitchen@atmel.com \
--cc=devicetree@vger.kernel.org \
--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
all inboxes | Powered by JetHome®