From: Tony Lindgren <tony@atomide.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Benoît Cousson" <bcousson@baylibre.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Vibhore Vardhan" <vibhore@ti.com>, "Dhruva Gole" <d-gole@ti.com>,
linux-omap@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 3/5] arm: dts: ti: omap: Fix OPP table node names
Date: Mon, 31 Jul 2023 09:25:51 +0300 [thread overview]
Message-ID: <20230731062551.GH5194@atomide.com> (raw)
In-Reply-To: <20230724153911.1376830-4-nm@ti.com>
* Nishanth Menon <nm@ti.com> [230724 15:39]:
> Fix the opp table node names for opps to be compliant with bindings.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
> Should probably go via Tony's tree.
Thanks applying patches 1 to 3 into omap-for-v6.6/dt.
Tony
next prev parent reply other threads:[~2023-07-31 6:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 15:39 [PATCH 0/5] dt-bindings: opp/cpufreq: Convert ti-cpufreq to Nishanth Menon
2023-07-24 15:39 ` [PATCH 1/5] arm: dts: ti: omap: omap36xx: Rename opp_supply nodename Nishanth Menon
2023-07-28 7:52 ` Dhruva Gole
2023-07-24 15:39 ` [PATCH 2/5] arm: dts: ti: omap: am5729-beagleboneai: Drop the OPP Nishanth Menon
2023-07-24 15:39 ` [PATCH 3/5] arm: dts: ti: omap: Fix OPP table node names Nishanth Menon
2023-07-31 6:25 ` Tony Lindgren [this message]
2023-07-24 15:39 ` [PATCH 4/5] dt-bindings: opp: Convert ti-omap5-opp-supply.txt to yaml binding Nishanth Menon
2023-07-26 17:10 ` Rob Herring
2023-07-26 19:15 ` Nishanth Menon
2023-07-24 15:39 ` [PATCH 5/5] dt-bindings: cpufreq: Convert ti-cpufreq.txt " Nishanth Menon
2023-07-26 17:14 ` Rob Herring
2023-07-26 19:17 ` Nishanth Menon
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=20230731062551.GH5194@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.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-omap@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
--cc=vibhore@ti.com \
--cc=viresh.kumar@linaro.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).