From: Rob Herring <robh@kernel.org>
To: Sergiu Moga <sergiu.moga@microchip.com>
Cc: krzysztof.kozlowski@canonical.com, devicetree@vger.kernel.org,
linux-i2c@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
nicolas.ferre@microchip.com, robh+dt@kernel.org,
claudiu.beznea@microchip.com
Subject: Re: [PATCH v2 2/3] dt-bindings: i2c: convert i2c-at91 to json-schema
Date: Thu, 10 Mar 2022 17:26:19 -0600 [thread overview]
Message-ID: <YiqJG369C521YS7a@robh.at.kernel.org> (raw)
In-Reply-To: <20220310114553.184763-3-sergiu.moga@microchip.com>
On Thu, 10 Mar 2022 13:45:52 +0200, Sergiu Moga wrote:
> Convert I2C binding for Atmel/Microchip SoCs to Device Tree Schema
> format.
>
> Signed-off-by: Sergiu Moga <sergiu.moga@microchip.com>
> ---
> .../bindings/i2c/atmel,at91sam-i2c.yaml | 140 ++++++++++++++++++
> .../devicetree/bindings/i2c/i2c-at91.txt | 82 ----------
> 2 files changed, 140 insertions(+), 82 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/i2c/atmel,at91sam-i2c.yaml
> delete mode 100644 Documentation/devicetree/bindings/i2c/i2c-at91.txt
>
Applied, thanks!
next prev parent reply other threads:[~2022-03-10 23:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 11:45 [PATCH v2 0/3] dt-bindings: i2c: convert i2c-at91 to json-schema Sergiu Moga
2022-03-10 11:45 ` [PATCH v2 1/3] ARM: dts: at91: sama7g5: Swap `rx` and `tx` for `i2c` nodes Sergiu Moga
2022-04-13 16:36 ` Nicolas Ferre
2022-03-10 11:45 ` [PATCH v2 2/3] dt-bindings: i2c: convert i2c-at91 to json-schema Sergiu Moga
2022-03-10 23:26 ` Rob Herring [this message]
2022-03-10 11:45 ` [PATCH v2 3/3] dt-bindings: i2c: at91: Add SAMA7G5 compatible strings list Sergiu Moga
2022-03-10 23:26 ` 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=YiqJG369C521YS7a@robh.at.kernel.org \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sergiu.moga@microchip.com \
/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).