public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sukrut Bellary <sbellary@baylibre.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Tero Kristo <kristo@kernel.org>,
	Kevin Hilman <khilman@baylibre.com>,
	Andreas Kemnade <andreas@kemnade.info>,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] dt-bindings: clock: ti: convert to yaml
Date: Tue, 20 May 2025 14:55:48 -0500	[thread overview]
Message-ID: <20250520195548.GA1254638-robh@kernel.org> (raw)
In-Reply-To: <20250516081612.767559-1-sbellary@baylibre.com>

On Fri, May 16, 2025 at 01:16:09AM -0700, Sukrut Bellary wrote:
> Convert TI autoidle and fixed-factor-clock bindings to yaml. We are fixing
> binding warnings only. No change in the existing dts.
> 
> Changes in v2:
> 	Patch 1:
> 	- Dropped reg and example.
> 	- Updated description
> 	- Fixed the subject
> 	- Fixed line re-wrap.
> 
> 	Dropped clockdomain.yaml(patch 2 in v1). This will be taken
> 	  with prcm.txt binding conversion.
> 
> 	Patch 2:
> 	- Fixed ti,autoidle.yaml reference.
> 	- Added constraints.
> 	- Dropped description from clocks and clock-output-names.
> 
> 	Patch 3:
> 	- Restored the license.
> 
> Link to v1:
> 	https://lore.kernel.org/lkml/20250404014500.2789830-1-sbellary@baylibre.com/
> 
> Sukrut Bellary (3):
>   dt-bindings: clock: ti: Convert autoidle binding to yaml
>   dt-bindings: clock: ti: Convert fixed-factor-clock to yaml
>   dt-bindings: clock: ti: add ti,autoidle.yaml reference

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>

      parent reply	other threads:[~2025-05-20 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-16  8:16 [PATCH v2 0/3] dt-bindings: clock: ti: convert to yaml Sukrut Bellary
2025-05-16  8:16 ` [PATCH v2 1/3] dt-bindings: clock: ti: Convert autoidle binding " Sukrut Bellary
2025-05-16  9:56   ` Rob Herring (Arm)
2025-06-11 16:17   ` Stephen Boyd
2025-05-16  8:16 ` [PATCH v2 2/3] dt-bindings: clock: ti: Convert fixed-factor-clock " Sukrut Bellary
2025-06-11 16:17   ` Stephen Boyd
2025-05-16  8:16 ` [PATCH v2 3/3] dt-bindings: clock: ti: add ti,autoidle.yaml reference Sukrut Bellary
2025-06-11 16:17   ` Stephen Boyd
2025-05-20 19:55 ` Rob Herring [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=20250520195548.GA1254638-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=andreas@kemnade.info \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sbellary@baylibre.com \
    --cc=sboyd@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