From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Arnd Bergmann <arnd@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
SoC Team <soc@kernel.org>, arm-soc <arm@kernel.org>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
Olof Johansson <olof@lixom.net>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Subject: Re: [GIT PULL] ARM: at91: soc for 5.12
Date: Fri, 22 Jan 2021 18:05:23 +0100 [thread overview]
Message-ID: <7131cfc0-2519-8bbe-a380-609eced61753@microchip.com> (raw)
In-Reply-To: <20210122163520.GG1196852@piout.net>
On 22/01/2021 at 17:35, Alexandre Belloni wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>
> On 22/01/2021 16:25:47+0100, Arnd Bergmann wrote:
>> On Fri, Jan 22, 2021 at 3:35 PM <nicolas.ferre@microchip.com> wrote:
>>>
>>> From: Nicolas Ferre <nicolas.ferre@microchip.com>
>>>
>>> Arnd, Olof,
>>>
>>> I'm taking back the lead on sending the pull-requests for AT91 and hope that I
>>> didn't loose the knowledge in the meantime. Tell me if there's something I'm
>>> missing. Thanks a lot to Alexandre who kept our flow steady and very
>>> predictable during all those years!
>>>
>>> Here are the first SoC changes for 5.12 which contain a single patch for multi
>>> platform kernels.
>>>
>>> I plan to send another pull-request for the SoC changes related to new sama7g5
>>> that Claudiu sent to the mainling-list recently. I'll let it mature in
>>> linux-next by the beginning of next week and will send another pull-request by
>>> mid-next-week.
>>> Tell me if you see a problem with this approach.
>>
>> This all looks good to me, but I think I'd rather take the 'soc' pull request
>> into the v5.11 bugfixes, as this may already affect users on other machines.
>>
>> I would also suggest adding a 'Cc: stable@vger.kernel.org' tag. If you like,
>> I can just cherry-pick that patch into the fixes branch and add it there.
>>
>
> I wouldn't backport it as a fix, this is just a warning, in a
> configuration that is very unlikely to be used (and honestly, I
> wouldn't enable this driver on any platform).
>
> If you take it as a fix, you'll have to also get
> https://lore.kernel.org/linux-arm-kernel/1611318097-8970-5-git-send-email-claudiu.beznea@microchip.com/
Arnd, Alexandre,
Whatever you prefer is fine with me. As I'm not the first impacted I
wouldn't push in one direction or another.
Best regards,
--
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-01-22 17:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-22 14:35 [GIT PULL] ARM: at91: soc for 5.12 nicolas.ferre
2021-01-22 15:25 ` Arnd Bergmann
2021-01-22 16:14 ` Nicolas Ferre
2021-01-22 16:35 ` Alexandre Belloni
2021-01-22 17:05 ` Nicolas Ferre [this message]
2021-01-22 22:36 ` Arnd Bergmann
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=7131cfc0-2519-8bbe-a380-609eced61753@microchip.com \
--to=nicolas.ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--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