From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Olof Johansson <olof@lixom.net>, arm-soc <arm@kernel.org>,
SoC Team <soc@kernel.org>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Eugen Hristev <eugen.hristev@microchip.com>
Subject: Re: [GIT PULL] ARM: at91: defconfig for 5.15
Date: Mon, 9 Aug 2021 15:41:32 +0200 [thread overview]
Message-ID: <5f5e8843-1a07-760a-db1a-aee084f00405@microchip.com> (raw)
Message-ID: <20210809134132.xocYF-Fa1zJ5teBzvkX5VLVhLBDUKLQ6daAGSlsHk_o@z> (raw)
In-Reply-To: <CAK8P3a1Ru-qawBWtbmfJm-jiPpJTRJ9zSufXHNCZvxt1RCMFBA@mail.gmail.com>
On 04/08/2021 at 16:02, Arnd Bergmann wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On Wed, Aug 4, 2021 at 10:46 AM <nicolas.ferre@microchip.com> wrote:
>> AT91 defconfig for 5.15:
>>
>> - add defconfig entries for new SoC: SAMA7G5
>> - dedicated sama7_defconfig to match the needed peripherals and
>> dependencies
>
> I feel this needs better description in the changelog: Why do you need another
> defconfig file in addition to the existing sama5_defconfig? Are they so
> different that a single config is not a good fit for both?
Hi Arnd,
I'm pushing another tag for this with better description. I hope it's
convincing ;-)
Best regards,
Nicolas
--
Nicolas Ferre
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-08-09 13:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 8:46 [GIT PULL] ARM: at91: defconfig for 5.15 nicolas.ferre
2021-08-04 8:46 ` nicolas.ferre
2021-08-04 14:02 ` Arnd Bergmann
2021-08-04 14:02 ` Arnd Bergmann
2021-08-04 14:02 ` Arnd Bergmann
2021-08-09 13:41 ` Nicolas Ferre [this message]
2021-08-09 13:41 ` Nicolas Ferre
2021-08-09 13:45 ` [GIT PULL v2] " nicolas.ferre
2021-08-09 13:45 ` nicolas.ferre
2021-08-12 21:08 ` Arnd Bergmann
2021-08-12 21:08 ` Arnd Bergmann
2021-08-12 21:20 ` patchwork-bot+linux-soc
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=5f5e8843-1a07-760a-db1a-aee084f00405@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=eugen.hristev@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=olof@lixom.net \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).