From: Rob Herring <robh@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Peter Rosin <peda@axentia.se>,
devicetree@vger.kernel.org, Andrew Jeffery <andrew@aj.id.au>,
Joel Stanley <joel@jms.id.au>, Wolfram Sang <wsa@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-tegra@vger.kernel.org, linux-i2c@vger.kernel.org,
Brendan Higgins <brendanhiggins@google.com>
Subject: Re: [PATCH 4/4] dt-bindings: i2c: i2c-mux-gpio: Convert to json-schema
Date: Fri, 17 Dec 2021 16:36:48 -0600 [thread overview]
Message-ID: <Yb0RABwvuSr56coI@robh.at.kernel.org> (raw)
In-Reply-To: <20211217165658.2650677-4-thierry.reding@gmail.com>
On Fri, 17 Dec 2021 17:56:58 +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> Convert the GPIO-based I2C mux bindings from the free-form text format
> to json-schema.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../devicetree/bindings/i2c/i2c-mux-gpio.txt | 80 --------------
> .../devicetree/bindings/i2c/i2c-mux-gpio.yaml | 103 ++++++++++++++++++
> 2 files changed, 103 insertions(+), 80 deletions(-)
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-gpio.txt
> create mode 100644 Documentation/devicetree/bindings/i2c/i2c-mux-gpio.yaml
>
Applied, thanks!
next prev parent reply other threads:[~2021-12-17 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 16:56 [PATCH v2 1/4] dt-bindings: i2c: tegra: Convert to json-schema Thierry Reding
2021-12-17 16:56 ` [PATCH 2/4] dt-bindings: i2c: i2c-mux-pinctrl: " Thierry Reding
2021-12-17 22:30 ` Rob Herring
2021-12-17 16:56 ` [PATCH 3/4] dt-bindings: i2c: aspeed: Document interrupt controller properties Thierry Reding
2021-12-17 22:35 ` Rob Herring
2021-12-17 16:56 ` [PATCH 4/4] dt-bindings: i2c: i2c-mux-gpio: Convert to json-schema Thierry Reding
2021-12-17 22:36 ` Rob Herring [this message]
2021-12-17 22:29 ` [PATCH v2 1/4] dt-bindings: i2c: tegra: " Rob Herring
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=Yb0RABwvuSr56coI@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=andrew@aj.id.au \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=wsa@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;
as well as URLs for NNTP newsgroup(s).