From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Paweł Anikiel" <pan@semihalf.com>,
soc@kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: arnd@arndb.de, olof@lixom.net, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, dinguyen@kernel.org,
amstan@chromium.org, upstream@semihalf.com
Subject: Re: [PATCH v2 1/5] ARM: dts: socfpga: Change Mercury+ AA1 dts to dtsi
Date: Thu, 2 Jun 2022 08:39:27 +0200 [thread overview]
Message-ID: <a6be8605-e538-d74b-b1b1-66766cf6bec3@linaro.org> (raw)
In-Reply-To: <20220601154647.80071-2-pan@semihalf.com>
On 01/06/2022 17:46, Paweł Anikiel wrote:
> The Mercury+ AA1 is not a standalone board, rather it's a module
> with an Arria 10 SoC. Remove status = "okay" and i2c aliases, as they
> are routed to the base board and should be enabled from there.
>
> Signed-off-by: Paweł Anikiel <pan@semihalf.com>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-06-02 6:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 15:46 [PATCH v2 0/5] Add Chameleon v3 devicetree Paweł Anikiel
2022-06-01 15:46 ` [PATCH v2 1/5] ARM: dts: socfpga: Change Mercury+ AA1 dts to dtsi Paweł Anikiel
2022-06-02 6:39 ` Krzysztof Kozlowski [this message]
2022-06-01 15:46 ` [PATCH v2 2/5] ARM: dts: socfpga: Move sdmmc-ecc node to Arria 10 dts Paweł Anikiel
2022-06-02 6:39 ` Krzysztof Kozlowski
2022-06-01 15:46 ` [PATCH v2 3/5] ARM: dts: socfpga: Add atsha204a node to Mercury+ AA1 dts Paweł Anikiel
2022-06-02 6:40 ` Krzysztof Kozlowski
2022-06-01 15:46 ` [PATCH v2 4/5] ARM: dts: socfpga: Add Google Chameleon v3 devicetree Paweł Anikiel
2022-06-02 6:41 ` Krzysztof Kozlowski
2022-06-01 15:46 ` [PATCH v2 5/5] dt-bindings: altera: Add Chameleon v3 board Paweł Anikiel
2022-06-02 6:42 ` Krzysztof Kozlowski
2022-06-01 19:26 ` [PATCH v2 0/5] Add Chameleon v3 devicetree 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=a6be8605-e538-d74b-b1b1-66766cf6bec3@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=amstan@chromium.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pan@semihalf.com \
--cc=robh+dt@kernel.org \
--cc=soc@kernel.org \
--cc=upstream@semihalf.com \
/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).