From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Chris Brandt <chris.brandt@renesas.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
Linux I2C <linux-i2c@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>
Subject: Re: [PATCH/RFC 0/4] dt-bindings: i2c: renesas,riic: Add interrupt-names
Date: Wed, 11 Aug 2021 21:04:12 +0200 [thread overview]
Message-ID: <YRQfLN3r0gFiQMG1@kunai> (raw)
In-Reply-To: <CAMuHMdVmKuYo7XhrQsLhXCOyRa=-aKwbtub=yi5nuSvJ22An2Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
Hi Geert,
> Probably it is not worth doing this in lockstep (1/4 in v5.15 through
> i2c, 2/4 and 3/4 in v5.16 through renesas-devel, and 4/4 in v5.17
> through i2c).
I agree!
> I have different branches for DT binding and DTS, but I guess it
> doesn't hurt to deviate and apply both to renesas-arm-dt-for-v5.15...
Sounds good, thanks!
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2021-08-11 19:04 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
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 [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=YRQfLN3r0gFiQMG1@kunai \
--to=wsa+renesas@sang-engineering.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=chris.brandt@renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=robh+dt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.