From: Simon Horman <horms@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v2] arm: dts: st: stm32mp151a-prtt1l: Fix QSPI configuration
Date: Sun, 11 Aug 2024 15:41:47 +0100 [thread overview]
Message-ID: <20240811144147.GL1951@kernel.org> (raw)
In-Reply-To: <20240810095129.GH1951@kernel.org>
On Sat, Aug 10, 2024 at 10:51:29AM +0100, Simon Horman wrote:
> On Fri, Aug 09, 2024 at 10:21:46AM +0200, Oleksij Rempel wrote:
> > Rename 'pins1' to 'pins' in the qspi_bk1_pins_a node to correct the
> > subnode name. The incorrect name caused the configuration to be
> > applied to the wrong subnode, resulting in QSPI not working properly.
> >
> > To avoid this kind of regression, all references to pin configuration
> > nodes are now referenced directly using the format &{label/subnode}.
> >
> > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
>
> Pass
Sorry about the noise here. This was supposed to be a note to myself, that
I am not planning to review this. It doesn't imply anything about the
patch.
next prev parent reply other threads:[~2024-08-11 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 8:21 [PATCH v2] arm: dts: st: stm32mp151a-prtt1l: Fix QSPI configuration Oleksij Rempel
2024-08-10 9:51 ` Simon Horman
2024-08-11 14:41 ` Simon Horman [this message]
2024-08-12 8:55 ` Ahmad Fatoum
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=20240811144147.GL1951@kernel.org \
--to=horms@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).