mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Maxime Coquelin <mcoquelin.stm32@gmail.com>,
	"Christoph Niedermaier" <cniedermaier@dh-electronics.com>,
	Marek Vasut <marex@denx.de>, <devicetree@vger.kernel.org>,
	<linux-stm32@st-md-mailman.stormreply.com>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <kernel@dh-electronics.com>
Subject: Re: [PATCH] arm: dts: stm32: Drop redundant status=okay
Date: Wed, 3 Sep 2025 10:31:18 +0200	[thread overview]
Message-ID: <0dbcc59d-2797-4106-b247-9bd575c5de2c@foss.st.com> (raw)
In-Reply-To: <20250818143730.244379-2-krzysztof.kozlowski@linaro.org>

Hi

On 8/18/25 16:37, Krzysztof Kozlowski wrote:
> Device nodes are enabled by default, so remove confusing or duplicated
> enabling of few nodes.  No practical impact, verified with dtx_diff.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>   arch/arm/boot/dts/st/stm32mp157c-dk2.dts          | 2 --
>   arch/arm/boot/dts/st/stm32mp157f-dk2.dts          | 2 --
>   arch/arm/boot/dts/st/stm32mp15xx-dhcom-drc02.dtsi | 1 -
>   arch/arm/boot/dts/st/stm32mp15xx-dhcom-pdk2.dtsi  | 3 ---
>   arch/arm/boot/dts/st/stm32mp15xx-dhcom-som.dtsi   | 2 --
>   5 files changed, 10 deletions(-)
> 

Applied on stm32-next.

thanks
Alex

      parent reply	other threads:[~2025-09-03  8:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 14:37 Krzysztof Kozlowski
2025-08-18 14:45 ` Marek Vasut
2025-08-18 14:51   ` Krzysztof Kozlowski
2025-08-18 14:56     ` Krzysztof Kozlowski
2025-08-18 14:58       ` Marek Vasut
2025-09-03  8:31 ` Alexandre TORGUE [this message]

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=0dbcc59d-2797-4106-b247-9bd575c5de2c@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=cniedermaier@dh-electronics.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@dh-electronics.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=marex@denx.de \
    --cc=mcoquelin.stm32@gmail.com \
    --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
all inboxes | Powered by JetHome®