public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Heiko Stübner" <heiko@sntech.de>
To: Lukasz Czechowski <lukasz.czechowski@thaumatec.com>,
	linux-arm-kernel@lists.infradead.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	Quentin Schulz <quentin.schulz@cherry.de>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: Move uart5 pin configuration to SoM dtsi
Date: Tue, 21 Jan 2025 10:38:28 +0100	[thread overview]
Message-ID: <3355298.oiGErgHkdL@diego> (raw)
In-Reply-To: <2d80ae4a-f836-4492-997c-69dac32be41b@cherry.de>

Am Dienstag, 21. Januar 2025, 10:36:15 CET schrieb Quentin Schulz:
> Hi Lukasz,
> 
> On 1/21/25 10:22 AM, Lukasz Czechowski wrote:
> > In the PX30-uQ7 (Ringneck) SoM, the hardware CTS and RTS pins for
> > uart5 cannot be used for the UART CTS/RTS, because they are already
> > allocated for different purposes. CTS pin is routed to SUS_S3#
> > signal, while RTS pin is used internally and is not available on
> > Q7 connector. Move definition of the pinctrl-0 property from
> > px30-ringneck-haikou.dts to px30-ringneck.dtsi.
> > 
> > Signed-off-by: Lukasz Czechowski <lukasz.czechowski@thaumatec.com>
> 
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
> 
> Considering that I'll request the next patch to be backported to stable 
> releases, we should probably backport this one as well to avoid a git 
> conflict?
> 
> c.f. 
> https://www.kernel.org/doc/html/latest/process/submitting-patches.html#select-the-recipients-for-your-patch
> 
> Essentially: Cc: stable@vger.kernel.org
> 
> @Heiko, this one patch isn't really a genuine candidate for stable 
> backport as it's just moving things around but it'll result in a git 
> conflict when backporting the other patch, how is it usually done for 
> stable releases?

Just Cc-stable and possibly explain it being a dependency in the commit message.

And patch2 should ideally get a Fixes tag



  reply	other threads:[~2025-01-21  9:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-21  9:22 [PATCH 0/2] Disable DMA on secondary UART on PX30 Ringneck Lukasz Czechowski
2025-01-21  9:22 ` [PATCH 1/2] arm64: dts: rockchip: Move uart5 pin configuration to SoM dtsi Lukasz Czechowski
2025-01-21  9:36   ` Quentin Schulz
2025-01-21  9:38     ` Heiko Stübner [this message]
2025-01-21  9:22 ` [PATCH 2/2] arm64: dts: rockchip: Disable DMA for uart5 on px30-ringneck Lukasz Czechowski
2025-01-21  9:41   ` Quentin Schulz
2025-01-21 10:28     ` Łukasz Czechowski
2025-01-21 10:45       ` Quentin Schulz

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=3355298.oiGErgHkdL@diego \
    --to=heiko@sntech.de \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lukasz.czechowski@thaumatec.com \
    --cc=quentin.schulz@cherry.de \
    --cc=robh@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