public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	Zhang Ying-22455 <ying.zhang22455@nxp.com>
Subject: Re: [PATCH v2 01/10] arm64: dts: lx2160a: fix scl-gpios property name
Date: Tue, 14 Dec 2021 13:33:58 +0800	[thread overview]
Message-ID: <20211214053357.GE10916@dragon> (raw)
In-Reply-To: <20211203235446.8266-2-leoyang.li@nxp.com>

On Fri, Dec 03, 2021 at 05:54:37PM -0600, Li Yang wrote:
> From: Zhang Ying-22455 <ying.zhang22455@nxp.com>
> 
> Fix the typo in the property name.
> 
> Signed-off-by: Zhang Ying <ying.zhang22455@nxp.com>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>

Shouldn't we have a Fixes tag?

Shawn

> ---
>  arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
> index dc8661ebd1f6..2433e6f2eda8 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
> +++ b/arch/arm64/boot/dts/freescale/fsl-lx2160a.dtsi
> @@ -719,7 +719,7 @@ i2c0: i2c@2000000 {
>  			clock-names = "i2c";
>  			clocks = <&clockgen QORIQ_CLK_PLATFORM_PLL
>  					    QORIQ_CLK_PLL_DIV(16)>;
> -			scl-gpio = <&gpio2 15 GPIO_ACTIVE_HIGH>;
> +			scl-gpios = <&gpio2 15 GPIO_ACTIVE_HIGH>;
>  			status = "disabled";
>  		};
>  
> @@ -768,7 +768,7 @@ i2c4: i2c@2040000 {
>  			clock-names = "i2c";
>  			clocks = <&clockgen QORIQ_CLK_PLATFORM_PLL
>  					    QORIQ_CLK_PLL_DIV(16)>;
> -			scl-gpio = <&gpio2 16 GPIO_ACTIVE_HIGH>;
> +			scl-gpios = <&gpio2 16 GPIO_ACTIVE_HIGH>;
>  			status = "disabled";
>  		};
>  
> -- 
> 2.25.1
> 

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-12-14  5:35 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 23:54 [PATCH v2 00/10] lx216x DTS updates Li Yang
2021-12-03 23:54 ` [PATCH v2 01/10] arm64: dts: lx2160a: fix scl-gpios property name Li Yang
2021-12-14  5:33   ` Shawn Guo [this message]
2021-12-03 23:54 ` [PATCH v2 02/10] arm64: dts: lx2160a-rdb: Add Inphi PHY node Li Yang
2021-12-03 23:54 ` [PATCH v2 03/10] arm64: dts: lx2160a: add optee-tz node Li Yang
2021-12-03 23:54 ` [PATCH v2 04/10] arm64: dts: lx2160a-qds: Add mdio mux nodes Li Yang
2021-12-03 23:54 ` [PATCH v2 05/10] arm64: dts: lx2160a: update PCIe nodes to match rev2 silicon Li Yang
2021-12-14  5:39   ` Shawn Guo
2021-12-14  6:14     ` Leo Li
2021-12-03 23:54 ` [PATCH v2 06/10] arm64: dts: lx2160a: add pcie EP mode nodes Li Yang
2021-12-14  5:40   ` Shawn Guo
2021-12-03 23:54 ` [PATCH v2 07/10] arm64: dts: lx2160a: enable usb3-lpm-capable for usb3 nodes Li Yang
2021-12-03 23:54 ` [PATCH v2 08/10] arm64: dts: lx2162a-qds: support SD UHS-I and eMMC HS400 modes Li Yang
2021-12-03 23:54 ` [PATCH v2 09/10] arm64: dts: lx2162a-qds: add interrupt line for RTC node Li Yang
2021-12-03 23:54 ` [PATCH v2 10/10] arm64: dts: lx2162a-qds: enable CAN nodes Li Yang
2021-12-06  5:58   ` Kuldeep Singh

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=20211214053357.GE10916@dragon \
    --to=shawnguo@kernel.org \
    --cc=leoyang.li@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ying.zhang22455@nxp.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