From: Marek Vasut <marex@denx.de>
To: patrice.chotard@foss.st.com, robh+dt@kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
alexandre.torgue@foss.st.com
Cc: mcoquelin.stm32@gmail.com,
linux-stm32@st-md-mailman.stormreply.com, linux@armlinux.org.uk,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@st.com>,
Reinhold Mueller <reinhold.mueller@emtrion.com>,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH 0/4] Fix qspi pinctrl phandle for stm3mp15 based boards
Date: Mon, 12 Dec 2022 13:59:43 +0100 [thread overview]
Message-ID: <11bcaf2e-864b-0f86-645e-5a1a619865a6@denx.de> (raw)
In-Reply-To: <20221212085142.3944367-1-patrice.chotard@foss.st.com>
On 12/12/22 09:51, patrice.chotard@foss.st.com wrote:
> From: Patrice Chotard <patrice.chotard@foss.st.com>
>
> qspi_bk1_pins_a and qspi_bk2_pins_a pinctrl phandle has been splitted in
> 2 parts. Only stm32mp157c-ev1.dts has been updated properly.
>
> Fix qspi pinctrl phandle for other boards which are based on stm32mp15x SoC.
Typo in $SUBJECT, s@stm3mp@stm32mp@ . That's in all the patches.
next prev parent reply other threads:[~2022-12-12 13:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 8:51 patrice.chotard
2022-12-12 8:51 ` [PATCH 1/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp15xx-dhcor-som patrice.chotard
2022-12-12 13:01 ` Marek Vasut
2022-12-12 8:51 ` [PATCH 2/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp15xx-dhcom-som patrice.chotard
2022-12-12 13:01 ` Marek Vasut
2022-12-12 8:51 ` [PATCH 3/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp157c-emstamp-argon patrice.chotard
2022-12-12 8:51 ` [PATCH 4/4] ARM: dts: stm32: Fix qspi pinctrl phandle for stm32mp151a-prtt1l patrice.chotard
2022-12-12 12:59 ` Marek Vasut [this message]
2023-01-09 16:26 ` [PATCH 0/4] Fix qspi pinctrl phandle for stm3mp15 based boards Alexandre TORGUE
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=11bcaf2e-864b-0f86-645e-5a1a619865a6@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=alexandre.torgue@st.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=linux@armlinux.org.uk \
--cc=mcoquelin.stm32@gmail.com \
--cc=o.rempel@pengutronix.de \
--cc=patrice.chotard@foss.st.com \
--cc=reinhold.mueller@emtrion.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
all inboxes | Powered by JetHome®