All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-i2c@vger.kernel.org, linux-rockchip@lists.infradead.org,
	devicetree@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 1/1] dt-bindings: i2c: i2c-rk3x: add rk3588 compatible
Date: Thu, 7 Jul 2022 23:09:13 +0200	[thread overview]
Message-ID: <YsdLeaGJGf7FFIK1@shikoro> (raw)
In-Reply-To: <20220623163136.246404-1-sebastian.reichel@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 250 bytes --]

On Thu, Jun 23, 2022 at 06:31:36PM +0200, Sebastian Reichel wrote:
> Just like RK356x, RK3588 is compatible to the existing rk3399 binding.
> 
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

Applied to for-next, thanks!


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa@kernel.org>
To: Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-i2c@vger.kernel.org, linux-rockchip@lists.infradead.org,
	devicetree@vger.kernel.org, kernel@collabora.com
Subject: Re: [PATCH 1/1] dt-bindings: i2c: i2c-rk3x: add rk3588 compatible
Date: Thu, 7 Jul 2022 23:09:13 +0200	[thread overview]
Message-ID: <YsdLeaGJGf7FFIK1@shikoro> (raw)
In-Reply-To: <20220623163136.246404-1-sebastian.reichel@collabora.com>


[-- Attachment #1.1: Type: text/plain, Size: 250 bytes --]

On Thu, Jun 23, 2022 at 06:31:36PM +0200, Sebastian Reichel wrote:
> Just like RK356x, RK3588 is compatible to the existing rk3399 binding.
> 
> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.com>

Applied to for-next, thanks!


[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 170 bytes --]

_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

  parent reply	other threads:[~2022-07-07 21:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-23 16:31 [PATCH 1/1] dt-bindings: i2c: i2c-rk3x: add rk3588 compatible Sebastian Reichel
2022-06-23 16:31 ` Sebastian Reichel
2022-06-26 20:22 ` Krzysztof Kozlowski
2022-06-26 20:22   ` Krzysztof Kozlowski
2022-07-06 19:34   ` Wolfram Sang
2022-07-06 19:34     ` Wolfram Sang
2022-07-06 19:55     ` Krzysztof Kozlowski
2022-07-06 19:55       ` Krzysztof Kozlowski
2022-07-07  0:11       ` Sebastian Reichel
2022-07-07  0:11         ` Sebastian Reichel
2022-07-07 21:09 ` Wolfram Sang [this message]
2022-07-07 21:09   ` 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=YsdLeaGJGf7FFIK1@shikoro \
    --to=wsa@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=kernel@collabora.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.reichel@collabora.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 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.