devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: sr@denx.de, krzysztof.kozlowski+dt@linaro.org,
	arinc.unal@arinc9.com, tsbogend@alpha.franken.de,
	devicetree@vger.kernel.org, robh+dt@kernel.org
Subject: Re: [PATCH v3] dt-bindings: i2c: migrate mt7621 text bindings to YAML
Date: Mon, 26 Sep 2022 14:08:34 -0500	[thread overview]
Message-ID: <20220926190834.GA2605301-robh@kernel.org> (raw)
In-Reply-To: <20220920052050.582321-1-sergio.paracuellos@gmail.com>

On Tue, 20 Sep 2022 07:20:50 +0200, Sergio Paracuellos wrote:
> SoC MT7621 I2C bindings used text format, so migrate them to YAML.
> There are some additions to the binding that were not in the original
> txt file. This binding is used in MT7621 and MT7628a Ralink SoCs. To
> properly match both dts nodes in tree we need to add to the schema
> 'clocks', 'clock-names' and 'reset-names'. Both 'clock-names' and
> 'reset-names' use 'i2c' as string so maintain that as const in
> the schema. Also, Properly update MAINTAINERS file to align the
> changes.
> 
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> Changes in v3:
> - Address review comment from Krzysztof:
>     - Rebase onto last kernel version.
>     - Drop address-cells and size-cells.
>     - Properly explain deviations from txt in commit message.
>     - Drop reset-names as required property.
>     - Squash previous series two commits in one to be bisectable.
> 
> Changes in v2:
> - Maintain current maintainer Stefan Rose as listed in kernel MAINTAINERS file.
>  .../devicetree/bindings/i2c/i2c-mt7621.txt    | 25 --------
>  .../bindings/i2c/mediatek,mt7621-i2c.yaml     | 61 +++++++++++++++++++
>  MAINTAINERS                                   |  2 +-
>  3 files changed, 62 insertions(+), 26 deletions(-)
>  delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-mt7621.txt
>  create mode 100644 Documentation/devicetree/bindings/i2c/mediatek,mt7621-i2c.yaml
> 

Applied, thanks!

      parent reply	other threads:[~2022-09-26 19:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-20  5:20 [PATCH v3] dt-bindings: i2c: migrate mt7621 text bindings to YAML Sergio Paracuellos
2022-09-21  6:47 ` Krzysztof Kozlowski
2022-09-21  7:07   ` Sergio Paracuellos
2022-09-26 19:08 ` 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=20220926190834.GA2605301-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=arinc.unal@arinc9.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=robh+dt@kernel.org \
    --cc=sergio.paracuellos@gmail.com \
    --cc=sr@denx.de \
    --cc=tsbogend@alpha.franken.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).