linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-i2c@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	devicetree@vger.kernel.org,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Chris Brandt <chris.brandt@renesas.com>,
	Rob Herring <robh+dt@kernel.org>,
	Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH/RFC 4/4] dt-bindings: i2c: renesas,riic: Make interrupt-names required
Date: Fri, 16 Jul 2021 13:20:24 -0600	[thread overview]
Message-ID: <20210716192024.GA3831653@robh.at.kernel.org> (raw)
In-Reply-To: <da8d1973dcd419d8d9c8c662ee614952f3a6969e.1626267422.git.geert+renesas@glider.be>

On Wed, 14 Jul 2021 15:20:03 +0200, Geert Uytterhoeven wrote:
> Now the I2C device nodes in all DTS files have gained "interrupt-names"
> properties, the "interrupt-names" property can be made required.
> 
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
>  Documentation/devicetree/bindings/i2c/renesas,riic.yaml | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2021-07-16 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-14 13:19 [PATCH/RFC 0/4] dt-bindings: i2c: renesas,riic: Add interrupt-names Geert Uytterhoeven
2021-07-14 13:20 ` [PATCH/RFC 1/4] " Geert Uytterhoeven
2021-07-16 19:19   ` Rob Herring
2021-07-14 13:20 ` [PATCH/RFC 2/4] ARM: dts: rza: Add I2C interrupt-names Geert Uytterhoeven
2021-07-14 13:20 ` [PATCH/RFC 3/4] arm64: dts: renesas: r9a07g044: " Geert Uytterhoeven
2021-07-14 17:21   ` Biju Das
2021-07-14 13:20 ` [PATCH/RFC 4/4] dt-bindings: i2c: renesas,riic: Make interrupt-names required Geert Uytterhoeven
2021-07-16 19:20   ` Rob Herring [this message]
2021-08-11 14:23 ` [PATCH/RFC 0/4] dt-bindings: i2c: renesas,riic: Add interrupt-names Wolfram Sang
2021-08-11 15:29   ` Geert Uytterhoeven
2021-08-11 19:04     ` Wolfram Sang

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=20210716192024.GA3831653@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=chris.brandt@renesas.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=robh+dt@kernel.org \
    --cc=wsa+renesas@sang-engineering.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).