From: Krzysztof Kozlowski <krzk@kernel.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,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: arm: qcom: add Linksys EA9350 V3
Date: Wed, 2 Oct 2024 14:23:24 +0200 [thread overview]
Message-ID: <f5265bcb-aa25-4bd7-a177-c980be1eee7a@kernel.org> (raw)
In-Reply-To: <20241002120804.25068-3-exxxxkc@getgoogleoff.me>
On 02/10/2024 14:08, Karl Chan wrote:
> Document linksys,jamaica for Linksys EA9350 V3.
>
> Signed-off-by: Karl Chan <exxxxkc@getgoogleoff.me>
> ---
> Documentation/devicetree/bindings/arm/qcom.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/qcom.yaml b/Documentation/devicetree/bindings/arm/qcom.yaml
> index 5cb54d69af0b..fa22f653a55f 100644
> --- a/Documentation/devicetree/bindings/arm/qcom.yaml
> +++ b/Documentation/devicetree/bindings/arm/qcom.yaml
> @@ -340,6 +340,7 @@ properties:
> - enum:
> - qcom,ipq5018-rdp432-c2
> - tplink,archer-ax55-v1
> + - linksys,jamaica
Keep alphabetical order.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-10-02 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 12:08 [PATCH 0/3] Initial for Linksys EA9350 V3 (linksys-jamaica) Karl Chan
2024-10-02 12:08 ` [PATCH 1/3] arm64: dts: qcom: add Linksys EA9350 V3 Karl Chan
2024-10-02 12:23 ` Krzysztof Kozlowski
2024-10-02 12:08 ` [PATCH 2/3] dt-bindings: arm: " Karl Chan
2024-10-02 12:23 ` Krzysztof Kozlowski [this message]
2024-10-02 12:08 ` [PATCH 3/3] arm: dts: qcom-ipq5018-linksys-jamaica: Include dts from arm64 Build the Linksys EA9350 V3 device trees from the arm64 tree together with the ARM32 include to allow booting this device on ARM32 Karl Chan
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=f5265bcb-aa25-4bd7-a177-c980be1eee7a@kernel.org \
--to=krzk@kernel.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=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).