From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Alexandre Belloni <alexandre.belloni@free-electrons.com>,
linux-arm-kernel@lists.infradead.org
Cc: plagnioj@jcrosoft.com, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, cyrille.pitchen@atmel.com
Subject: Re: [PATCH 3/3] ARM: at91/defconfig: update sama5 defconfig
Date: Thu, 15 Oct 2015 17:42:53 +0200 [thread overview]
Message-ID: <561FC97D.2040806@atmel.com> (raw)
In-Reply-To: <20151015153116.GE26893@odux.rfo.atmel.com>
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.
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2015-10-15 15:42 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
[not found] ` <1444824684-24526-1-git-send-email-ludovic.desroches-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
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
[not found] ` <20151015132451.GD3421-m++hUPXGwpdeoWH0uzbU5w@public.gmane.org>
2015-10-15 15:31 ` Ludovic Desroches
2015-10-15 15:42 ` Nicolas Ferre [this message]
2015-10-16 6:44 ` Ludovic Desroches
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=561FC97D.2040806@atmel.com \
--to=nicolas.ferre@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=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;
as well as URLs for NNTP newsgroup(s).