From: Conor Dooley <conor@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
arm@kernel.org, soc@kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzk@kernel.org>,
Lars Povlsen <lars.povlsen@microchip.com>,
Steen Hegelund <Steen.Hegelund@microchip.com>,
Conor Dooley <conor.dooley@microchip.com>,
Daniel Machon <daniel.machon@microchip.com>,
UNGLinuxDriver@microchip.com
Subject: Re: [GIT PULL 1/2] arm64: dts: cleanup and fixes for v6.5
Date: Thu, 18 May 2023 22:31:44 +0100 [thread overview]
Message-ID: <20230518-tactile-outback-f4ceeb36d68c@spud> (raw)
In-Reply-To: <20230517131255.471002-1-krzysztof.kozlowski@linaro.org>
[-- Attachment #1.1: Type: text/plain, Size: 481 bytes --]
On Wed, May 17, 2023 at 03:12:54PM +0200, Krzysztof Kozlowski wrote:
> There is ongoing discussion how to improve a bit Microchip ARM64 SparX-5 patch
> handling process, so the contributions won't get lost.
Aye, should be sorted. We'll add some arm64 specific branches in the
at91 repo & a patch has been sent for the related maintainers entries:
https://lore.kernel.org/all/20230517-shimmer-retry-34596c637882@spud/
Thanks Krzysztof for picking up these ones.
Cheers,
Conor.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-05-18 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-17 13:12 [GIT PULL 1/2] arm64: dts: cleanup and fixes for v6.5 Krzysztof Kozlowski
2023-05-17 13:12 ` [GIT PULL 2/2] ARM: dts: cleanup " Krzysztof Kozlowski
2023-05-18 21:31 ` Conor Dooley [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=20230518-tactile-outback-f4ceeb36d68c@spud \
--to=conor@kernel.org \
--cc=Steen.Hegelund@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=conor.dooley@microchip.com \
--cc=daniel.machon@microchip.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lars.povlsen@microchip.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--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