devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Fabio Estevam <festevam@denx.de>
Cc: linux-arm-kernel@lists.infradead.org,
	Jonas Kuenstler <j.kuenstler@phytec.de>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Peng Fan <peng.fan@nxp.com>, Rob Herring <robh+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Teresa Remmet <t.remmet@phytec.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: dts: imx8mp: Drop deprecated regulator-compatible from i.MX8M Plus PhyCore SoM
Date: Fri, 16 Dec 2022 01:36:45 +0100	[thread overview]
Message-ID: <5d67cfa2-4af3-39ea-2d3a-26ae7beffc03@denx.de> (raw)
In-Reply-To: <76040ae69860f88440dd9a558a6d2579@denx.de>

On 12/16/22 01:33, Fabio Estevam wrote:
> Hi Marek,

Hi,

> On 15/12/2022 20:57, Marek Vasut wrote:
>> The "regulator-compatible" property is deprecated and unused, as the
>> match happens on the node name in Linux of_regulator_match() in case
>> the property is not present. Drop the deprecated property from DT.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
> 
> Thanks for the patch.
> 
> I have already sent the same fix:
> 
> https://lore.kernel.org/linux-arm-kernel/20221121162911.2377556-1-festevam@gmail.com/T/

Ah nice, thanks !

Please drop this patch then.

  reply	other threads:[~2022-12-16  0:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 23:57 [PATCH 1/2] arm64: dts: imx8mp: Drop deprecated regulator-compatible from i.MX8M Plus DHCOM Marek Vasut
2022-12-15 23:57 ` [PATCH 2/2] arm64: dts: imx8mp: Drop deprecated regulator-compatible from i.MX8M Plus PhyCore SoM Marek Vasut
2022-12-16  0:33   ` Fabio Estevam
2022-12-16  0:36     ` Marek Vasut [this message]
2023-01-01  2:24 ` [PATCH 1/2] arm64: dts: imx8mp: Drop deprecated regulator-compatible from i.MX8M Plus DHCOM Shawn Guo

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=5d67cfa2-4af3-39ea-2d3a-26ae7beffc03@denx.de \
    --to=marex@denx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@denx.de \
    --cc=j.kuenstler@phytec.de \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=peng.fan@nxp.com \
    --cc=robh+dt@kernel.org \
    --cc=shawnguo@kernel.org \
    --cc=t.remmet@phytec.de \
    /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).