From: Neil Armstrong <neil.armstrong@linaro.org>
To: Igor Prusov <ivprusov@salutedevices.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Kevin Hilman <khilman@baylibre.com>
Cc: prusovigor@gmail.com, kernel@sberdevices.ru,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/2] arm64: dts: meson-a1-ad402: Add SPIFC pins
Date: Fri, 6 Oct 2023 08:39:11 +0200 [thread overview]
Message-ID: <bbca1c2f-2b7e-4132-a23e-12bd41abfec5@linaro.org> (raw)
In-Reply-To: <20231005195543.380273-1-ivprusov@salutedevices.com>
On 05/10/2023 21:55, Igor Prusov wrote:
> This series adds SPIFC pins description to A1 pinctrl node and selects
> them in AD402's SPIFC node to make sure that muxed GPIO is properly
> configured.
>
> Igor Prusov (2):
> arm64: dts: meson: a1: Add SPIFC mux pins
> arm64: dts: meson-a1-ad402: set SPIFC pins
>
> arch/arm64/boot/dts/amlogic/meson-a1-ad402.dts | 2 ++
> arch/arm64/boot/dts/amlogic/meson-a1.dtsi | 12 ++++++++++++
> 2 files changed, 14 insertions(+)
>
For the 2 patches:
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-10-06 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-05 19:55 [PATCH v1 0/2] arm64: dts: meson-a1-ad402: Add SPIFC pins Igor Prusov
2023-10-05 19:55 ` [PATCH v1 1/2] arm64: dts: meson: a1: Add SPIFC mux pins Igor Prusov
2023-10-05 19:55 ` [PATCH v1 2/2] arm64: dts: meson-a1-ad402: set SPIFC pins Igor Prusov
2023-10-06 6:39 ` Neil Armstrong [this message]
2023-10-06 6:43 ` [PATCH v1 0/2] arm64: dts: meson-a1-ad402: Add " Neil Armstrong
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=bbca1c2f-2b7e-4132-a23e-12bd41abfec5@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ivprusov@salutedevices.com \
--cc=jbrunet@baylibre.com \
--cc=kernel@sberdevices.ru \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=prusovigor@gmail.com \
--cc=robh+dt@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