From: Dhruva Gole <d-gole@ti.com>
To: Nishanth Menon <nm@ti.com>
Cc: "Rob Herring" <robh+dt@kernel.org>,
"Stephen Boyd" <sboyd@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Vibhore Vardhan" <vibhore@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 V2 2/2] dt-bindings: cpufreq: Convert ti-cpufreq to json schema
Date: Thu, 3 Aug 2023 11:31:35 +0530 [thread overview]
Message-ID: <20230803060135.cichqctmjhajt2hq@dhruva> (raw)
In-Reply-To: <20230801233341.1416552-3-nm@ti.com>
On Aug 01, 2023 at 18:33:41 -0500, Nishanth Menon wrote:
> Move the ti-cpufreq binding over to opp and convert convert the free
Minor nitpik, maybe can be fixed while applying the patch. Checkpatch caught this,
Possible repeated word: 'convert'
> text binding to json-schema.
>
> Signed-off-by: Nishanth Menon <nm@ti.com>
> ---
Otherwise, LGTM
Reviewed-by: Dhruva Gole <d-gole@ti.com>
> Changes since V1:
> - Fixup $subject of the patch to indicate json schema rather than yaml.
> - Change filename to matchup with binding compatible
> - Dropped un-used labels
> - Dropped "|" in "description"
>
> V1: https://lore.kernel.org/all/20230724153911.1376830-6-nm@ti.com/
>
> Side note: cleanups in dt is picked up on Tony's tree:
> https://lore.kernel.org/all/20230731062551.GH5194@atomide.com/
>
> .../bindings/cpufreq/ti-cpufreq.txt | 132 ------------------
> .../opp/operating-points-v2-ti-cpu.yaml | 88 ++++++++++++
> 2 files changed, 88 insertions(+), 132 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt
> create mode 100644 Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml
>
> diff --git a/Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt b/Documentation/devicetree/bindings/cpufreq/ti-cpufreq.txt
> deleted file mode 100644
[..snip..]
--
Best regards,
Dhruva Gole <d-gole@ti.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-03 6:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 23:33 [PATCH V2 0/2] dt-bindings: opp/cpufreq: Convert ti-cpufreq to json schema Nishanth Menon
2023-08-01 23:33 ` [PATCH V2 1/2] dt-bindings: opp: Convert ti-omap5-opp-supply " Nishanth Menon
2023-08-01 23:33 ` [PATCH V2 2/2] dt-bindings: cpufreq: Convert ti-cpufreq " Nishanth Menon
2023-08-03 6:01 ` Dhruva Gole [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=20230803060135.cichqctmjhajt2hq@dhruva \
--to=d-gole@ti.com \
--cc=bcousson@baylibre.com \
--cc=conor+dt@kernel.org \
--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=tony@atomide.com \
--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