From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 780C6C433EF for ; Thu, 7 Jul 2022 21:09:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236525AbiGGVJX (ORCPT ); Thu, 7 Jul 2022 17:09:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57242 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235575AbiGGVJV (ORCPT ); Thu, 7 Jul 2022 17:09:21 -0400 Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 071591C108; Thu, 7 Jul 2022 14:09:21 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ams.source.kernel.org (Postfix) with ESMTPS id B1FCCB823FD; Thu, 7 Jul 2022 21:09:19 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 8C348C3411E; Thu, 7 Jul 2022 21:09:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1657228158; bh=6krTAHwFw5x0U7lXZFEFY+uwkkZbcGAH15gDhbYLZwM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ga/Eg8he1VNjTwBK41B5yYfJYSptChGMWMA+R6lCpztF7tZajil53T7Qq6HpZskYi Dt66uiBvx/L6DBZoQhh3reKkpIXFjf9TEtHVu2iujHESQe6IqCKLdEv0b2qdCtzuAz QHro3r5Os2Q0y8XV/8KpK5CKWuXiCfjky1t5i08QIJk65RnbChP3oa37U3M960I+L1 CmmrOKdaQ8LtgMRp/ah3lp2UJTOziUimDe5XlODUkVFLelit+55xchlMFDiG7zyegi joDUwMMMnnHXHnVpYxVIBFHi6f6FxrXX8/7t/gREyg13EHBvgn4J2aJkM7bY1xCek0 3xXWMZ8DY5xMg== Date: Thu, 7 Jul 2022 23:09:13 +0200 From: Wolfram Sang To: Sebastian Reichel Cc: Heiko Stuebner , Rob Herring , Krzysztof Kozlowski , 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 Message-ID: Mail-Followup-To: Wolfram Sang , Sebastian Reichel , Heiko Stuebner , Rob Herring , Krzysztof Kozlowski , linux-i2c@vger.kernel.org, linux-rockchip@lists.infradead.org, devicetree@vger.kernel.org, kernel@collabora.com References: <20220623163136.246404-1-sebastian.reichel@collabora.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="6ILHCh8oIcB1AeoY" Content-Disposition: inline In-Reply-To: <20220623163136.246404-1-sebastian.reichel@collabora.com> Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org --6ILHCh8oIcB1AeoY Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 23, 2022 at 06:31:36PM +0200, Sebastian Reichel wrote: > Just like RK356x, RK3588 is compatible to the existing rk3399 binding. >=20 > Signed-off-by: Sebastian Reichel Applied to for-next, thanks! --6ILHCh8oIcB1AeoY Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEOZGx6rniZ1Gk92RdFA3kzBSgKbYFAmLHS3kACgkQFA3kzBSg KbZbdxAAh0HztJSdWzgE6pvvDl4NPTDHqvu/WoFDZb4u8b3JEuS5aBbnq/88tdXd ZvEuui8kTRfTdlFtOhg8Hwht0JDWR5gIxoQUn4t/wXos7pACFutNe2aB4PqgU+JR wG2rNirDX0xKW9zkUcZkSBH9cjvWxrAbUuAwiek+cc7jJvARTLe90PgVB7pe4yP8 rYPUEXXhLsBxQCTxneyiiqVhm0SrivIJtGBMg1ZenNxvcuwJheURRVakm4CTzw14 FMWMfCAYnqNvfw+4FiHKowrL0PzggoFCUZm/5Mn0mBa2cpj6nXtBpkahBwJ3qoZN wngs/Otsmsnzm5jyAjV3SlPuYjVpsWAvijkMIuGhIyLwHV19QTy7DkArTrpz4NKL r0u39rnxauNqnrV1uD+Nbl7vH6J6sowm94iDGb/Vv20DBFLRHPYBbxAU3dW9Iyjz HRJCKAKsDybpYcyIVp2gWWT9sINkYTxV0EQeNnCIJSCy8UUDc3zYcq/j5Nz4HYZt lMzEwSTUpdm1yzvFFk02ewmTkraoos4QouLuljCP2qsMdlhyvdl6RdS35Gt34iVE qncRgVU6s0Xq5ELw1H0VCsL4w3cI8LLGDcIA2lLg07PzrQ30hIakOPikmK6YL/Lw W70ueL4eaj8eFbU33cueytdy/W4/bWkw9Hz/DpD8f0/qriulrmA= =OzcX -----END PGP SIGNATURE----- --6ILHCh8oIcB1AeoY--