From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Karl Chan <exxxxkc@getgoogleoff.me>, linux-arm-msm@vger.kernel.org
Cc: andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, mturquette@baylibre.com,
sboyd@kernel.org, linus.walleij@linaro.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 5/5] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64
Date: Wed, 2 Oct 2024 18:17:27 +0200 [thread overview]
Message-ID: <b9ddef90-6f33-48ff-beaa-f1caa1a75ec2@linaro.org> (raw)
In-Reply-To: <20241002152419.30364-6-exxxxkc@getgoogleoff.me>
On 02/10/2024 17:24, Karl Chan wrote:
> Build the Linksys EA9350 V3 device trees from the arm64 tree together with the ARM32 include to allow booting this device on ARM32.
>
> The approach to include device tree files from other architectures is
> inspired from e.g. the Raspberry Pi (bcm2711-rpi-4-b.dts) where this is
> used to build the device tree for both ARM32 and ARM64.
>
> Signed-off-by: Karl Chan <exxxxkc@getgoogleoff.me>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
This did not happen. Drop all fake tags.
Please read again instructions in submitting patches.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-10-02 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 15:24 [PATCH v3 0/5] Initial Support for Linksys EA9350 V3 (linksys-jamaica) Karl Chan
2024-10-02 15:24 ` [PATCH v3 1/5] dt-bindings: arm: qcom: add Linksys EA9350 V3 Karl Chan
2024-10-02 15:24 ` [PATCH v3 2/5] arm64: dts: " Karl Chan
2024-10-02 15:24 ` [PATCH v3 3/5] clk: qcom: ipq5018: allow it to be bulid on arm32 Karl Chan
2024-10-02 15:24 ` [PATCH v3 4/5] pinctrl: " Karl Chan
2024-10-02 15:24 ` [PATCH v3 5/5] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64 Karl Chan
2024-10-02 16:17 ` Krzysztof Kozlowski [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=b9ddef90-6f33-48ff-beaa-f1caa1a75ec2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=exxxxkc@getgoogleoff.me \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@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).