From: Krzysztof Kozlowski <krzk@kernel.org>
To: Vladislav Leonov <vlad@zlab.su>
Cc: linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
Simon Glass <sjg@chromium.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, Andi Shyti <andi.shyti@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Rob Herring <robh@kernel.org>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH 11/25] dt-bindings: i2c: rk3x: Add RV1106 compatible
Date: Fri, 14 Aug 2026 12:21:12 +0200 [thread overview]
Message-ID: <20260814-resilient-handsome-ibis-d5efdd@quoll> (raw)
In-Reply-To: <20260810121121.210040-12-vlad@zlab.su>
On Mon, Aug 10, 2026 at 03:11:02PM +0300, Vladislav Leonov wrote:
> The RV1106 I2C controller is compatible with the one found on RK3399,
Add RV1106 I2C controller, which is compatible ... /
One sentence, one line or two lines.
> so add the "rockchip,rv1106-i2c" compatible to the list of variants
> that fall back to "rockchip,rk3399-i2c".
No need to repeat obvious parts of the diff. Explain non-obvious parts,
though, if they are.
Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-08-14 10:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-10 12:10 [PATCH 00/25] ARM: rockchip: Add peripheral support for RV1106 Vladislav Leonov
2026-08-10 12:11 ` [PATCH 11/25] dt-bindings: i2c: rk3x: Add RV1106 compatible Vladislav Leonov
2026-08-14 10:21 ` Krzysztof Kozlowski [this message]
2026-08-10 18:35 ` [PATCH 00/25] ARM: rockchip: Add peripheral support for RV1106 Jakub Kicinski
2026-08-11 5:43 ` Uwe Kleine-König
2026-08-11 15:53 ` Jakub Kicinski
2026-08-11 16:06 ` Mark Brown
2026-08-14 10:18 ` Krzysztof Kozlowski
2026-08-20 11:47 ` Simon Glass
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=20260814-resilient-handsome-ibis-d5efdd@quoll \
--to=krzk@kernel.org \
--cc=andi.shyti@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sjg@chromium.org \
--cc=vlad@zlab.su \
/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