From: Neil Armstrong <neil.armstrong@linaro.org>
To: FUKAUMI Naoki <naoki@radxa.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
khilman@baylibre.com, jbrunet@baylibre.com,
martin.blumenstingl@googlemail.com, devicetree@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: amlogic: add support for Radxa ZERO 2 Pro
Date: Thu, 22 Aug 2024 10:23:36 +0200 [thread overview]
Message-ID: <eacafb4c-ace9-429a-9359-1e2e602e5d7e@linaro.org> (raw)
In-Reply-To: <0D8F14444C69EB08+cfb9ef39-4243-4dd6-859f-98ca34e00e98@radxa.com>
On 22/08/2024 05:11, FUKAUMI Naoki wrote:
> Hi,
>
> I'm sorry, could you drop these patches from amlogic/linux.git?
>
> I changed my mind that adding new dts just for renaming product is wrong.
Ack, will drop the patches.
Neil
>
> Best regards,
>
> --
> FUKAUMI Naoki
> Radxa Computer (Shenzhen) Co., Ltd.
>
> On 8/21/24 00:30, Neil Armstrong wrote:
>> Hi,
>>
>> On Sat, 13 Jul 2024 06:51:10 +0900, FUKAUMI Naoki wrote:
>>> Radxa ZERO 2 Pro is a ultra tiny high performance SBC[1] using the
>>> Amlogic A311D chip.
>>>
>>> [1] https://radxa.com/products/zeros/zero2pro
>>>
>>>
>>
>> Thanks, Applied to https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git (v6.12/arm64-dt)
>>
>> [1/2] dt-bindings: arm: amlogic: add support for Radxa ZERO 2 Pro
>> https://git.kernel.org/amlogic/c/8f97ee0c9f5c6fc250847d7492875a6d7152ba68
>> [2/2] arm64: dts: amlogic: add support for Radxa ZERO 2 Pro
>> https://git.kernel.org/amlogic/c/69591796c5d585816a306134f6d565cf19da575e
>>
>> These changes has been applied on the intermediate git tree [1].
>>
>> The v6.12/arm64-dt branch will then be sent via a formal Pull Request to the Linux SoC maintainers
>> for inclusion in their intermediate git branches in order to be sent to Linus during
>> the next merge window, or sooner if it's a set of fixes.
>>
>> In the cases of fixes, those will be merged in the current release candidate
>> kernel and as soon they appear on the Linux master branch they will be
>> backported to the previous Stable and Long-Stable kernels [2].
>>
>> The intermediate git branches are merged daily in the linux-next tree [3],
>> people are encouraged testing these pre-release kernels and report issues on the
>> relevant mailing-lists.
>>
>> If problems are discovered on those changes, please submit a signed-off-by revert
>> patch followed by a corrective changeset.
>>
>> [1] https://git.kernel.org/pub/scm/linux/kernel/git/amlogic/linux.git
>> [2] https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
>> [3] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
>>
prev parent reply other threads:[~2024-08-22 8:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 21:51 [PATCH v3 1/2] dt-bindings: arm: amlogic: add support for Radxa ZERO 2 Pro FUKAUMI Naoki
2024-07-12 21:51 ` [PATCH v3 2/2] arm64: dts: " FUKAUMI Naoki
2024-08-20 15:22 ` neil.armstrong
2024-07-13 9:58 ` [PATCH v3 1/2] dt-bindings: arm: " Krzysztof Kozlowski
2024-08-20 15:30 ` Neil Armstrong
2024-08-22 3:11 ` FUKAUMI Naoki
2024-08-22 8:23 ` Neil Armstrong [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=eacafb4c-ace9-429a-9359-1e2e602e5d7e@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=naoki@radxa.com \
--cc=robh@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).