All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Stein <alexander.stein@ew.tq-group.com>
To: shawnguo@kernel.org, Fabio Estevam <festevam@denx.de>
Cc: linux-arm-kernel@lists.infradead.org, Fabio Estevam <festevam@denx.de>
Subject: Re: [PATCH] arm64: dts: mba8mx: Remove unneeded comments
Date: Thu, 02 Jun 2022 08:10:37 +0200	[thread overview]
Message-ID: <44773003.fMDQidcC6G@steina-w> (raw)
In-Reply-To: <20220601131928.319497-1-festevam@denx.de>

Am Mittwoch, 1. Juni 2022, 15:19:28 CEST schrieb Fabio Estevam:
> The bootargs line is already commented out and the comment of UART4
> does not apply, as uart4 node is not described.
> 
> Remove both comments to make the dtsi cleaner.
> 
> Signed-off-by: Fabio Estevam <festevam@denx.de>
> ---
>  arch/arm64/boot/dts/freescale/mba8mx.dtsi | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/freescale/mba8mx.dtsi
> b/arch/arm64/boot/dts/freescale/mba8mx.dtsi index
> c2f0f1a1566c..ea20b2a8aea8 100644
> --- a/arch/arm64/boot/dts/freescale/mba8mx.dtsi
> +++ b/arch/arm64/boot/dts/freescale/mba8mx.dtsi
> @@ -16,7 +16,6 @@ beeper {
>  	};
> 
>  	chosen {
> -		// bootargs = "console=ttymxc2,115200
> earlycon=ec_imx6q,0x30880000,115200"; stdout-path = &uart3;
>  	};
> 
> @@ -272,7 +271,6 @@ &uart3 {
>  	status = "okay";
>  };
> 
> -/* UART4 is assigned to Cortex-M4 */
>  &usdhc2 {
>  	pinctrl-names = "default", "state_100mhz", "state_200mhz";
>  	pinctrl-0 = <&pinctrl_usdhc2>, <&pinctrl_usdhc2_gpio>;

Reviewed-by: Alexander Stein <alexander.stein@ew.tq-group.com>




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

  reply	other threads:[~2022-06-02  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-01 13:19 [PATCH] arm64: dts: mba8mx: Remove unneeded comments Fabio Estevam
2022-06-02  6:10 ` Alexander Stein [this message]
2022-06-19  3:33 ` Shawn Guo

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=44773003.fMDQidcC6G@steina-w \
    --to=alexander.stein@ew.tq-group.com \
    --cc=festevam@denx.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=shawnguo@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.