mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexandre TORGUE <alexandre.torgue@foss.st.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>,
	<linux-kernel@vger.kernel.org>
Cc: linux-amarula@amarulasolutions.com,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
	"Raphaël Gallais-Pou" <raphael.gallais-pou@foss.st.com>,
	"Rob Herring" <robh+dt@kernel.org>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] ARM: dts: stm32: stm32f7-pinctrl: don't use multiple blank lines
Date: Fri, 22 Sep 2023 11:13:53 +0200	[thread overview]
Message-ID: <cb996f8a-16ad-96ec-11ed-993f494ef6b9@foss.st.com> (raw)
In-Reply-To: <20230904180341.923038-1-dario.binacchi@amarulasolutions.com>

Hi Dario

On 9/4/23 20:03, Dario Binacchi wrote:
> The patch fixes the following warning:
> 
> arch/arm/dts/stm32f7-pinctrl.dtsi:380: check: Please don't use multiple blank lines
> 
> Fixes: ba287d1a0137 ("ARM: dts: stm32: add pin map for LTDC on stm32f7")
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> 
> ---
> 
>   arch/arm/boot/dts/st/stm32f7-pinctrl.dtsi | 1 -
>   1 file changed, 1 deletion(-)
> 
> diff --git a/arch/arm/boot/dts/st/stm32f7-pinctrl.dtsi b/arch/arm/boot/dts/st/stm32f7-pinctrl.dtsi
> index 65480a9f5cc4..842f2b17c4a8 100644
> --- a/arch/arm/boot/dts/st/stm32f7-pinctrl.dtsi
> +++ b/arch/arm/boot/dts/st/stm32f7-pinctrl.dtsi
> @@ -376,7 +376,6 @@ pins2 {
>   				};
>   			};
>   
> -
>   			ltdc_pins_a: ltdc-0 {
>   				pins {
>   					pinmux = <STM32_PINMUX('E', 4, AF14)>, /* LCD_B0 */


Applied on stm32-next.

Thanks.
Alex

      parent reply	other threads:[~2023-09-22  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-04 18:03 Dario Binacchi
2023-09-05 11:36 ` Raphael Gallais-Pou
2023-09-22  9:13 ` Alexandre TORGUE [this message]

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=cb996f8a-16ad-96ec-11ed-993f494ef6b9@foss.st.com \
    --to=alexandre.torgue@foss.st.com \
    --cc=conor+dt@kernel.org \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-amarula@amarulasolutions.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=mcoquelin.stm32@gmail.com \
    --cc=raphael.gallais-pou@foss.st.com \
    --cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®