From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Rob Herring <robh+dt@kernel.org>,
Magnus Damm <magnus.damm@gmail.com>,
Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>,
linux-i2c@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, Rob Herring <robh@kernel.org>
Subject: Re: [PATCH v2 5/5] dt-bindings: i2c: renesas,iic: Convert to json-schema
Date: Sun, 20 Jun 2021 22:42:13 +0200 [thread overview]
Message-ID: <YM+oJa0XQUXv6oU/@kunai> (raw)
In-Reply-To: <8fc6fdb175d65306e601a4209944a99e1e6fcb09.1624013699.git.geert+renesas@glider.be>
[-- Attachment #1: Type: text/plain, Size: 456 bytes --]
On Fri, Jun 18, 2021 at 01:04:11PM +0200, Geert Uytterhoeven wrote:
> Convert the Renesas R-Mobile I2C Bus Interface (IIC) Device Tree binding
> documentation to json-schema.
>
> Document missing properties.
> R-Mobile A1 and SH-Mobile have multiple interrupts.
> Update the example to match reality.
>
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> Reviewed-by: Rob Herring <robh@kernel.org>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-06-20 20:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1624013699.git.geert+renesas@glider.be>
2021-06-18 11:04 ` [PATCH v2 1/5] dt-bindings: i2c: renesas,iic: Always declare generic compatibility Geert Uytterhoeven
2021-06-20 20:42 ` Wolfram Sang
2021-06-18 11:04 ` [PATCH v2 2/5] ARM: dts: rzg1: Add generic compatible strings to IIC nodes Geert Uytterhoeven
2021-06-18 11:04 ` [PATCH v2 3/5] arm64: dts: renesas: r8a774c0: Add generic compatible string to IIC node Geert Uytterhoeven
2021-06-18 11:04 ` [PATCH v2 4/5] arm64: dts: renesas: r8a77990: " Geert Uytterhoeven
2021-06-18 11:04 ` [PATCH v2 5/5] dt-bindings: i2c: renesas,iic: Convert to json-schema Geert Uytterhoeven
2021-06-20 20:42 ` Wolfram Sang [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=YM+oJa0XQUXv6oU/@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh+dt@kernel.org \
--cc=robh@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).