From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: Claudiu <claudiu.beznea@tuxon.dev>, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH RESEND 5.10.y 3/4] serial: sh-sci: Clean sci_ports[0] after at earlycon exit
Date: Wed, 11 Jun 2025 22:22:46 -0400 [thread overview]
Message-ID: <20250611110644-edcd669842126366@stable.kernel.org> (raw)
In-Reply-To: <20250611050053.454338-4-claudiu.beznea.uj@bp.renesas.com>
[ Sasha's backport helper bot ]
Hi,
✅ All tests passed successfully. No issues detected.
No action required from the submitter.
The upstream commit SHA1 provided is correct: 5f1017069933489add0c08659673443c9905659e
WARNING: Author mismatch between patch and upstream commit:
Backport author: Claudiu<claudiu.beznea@tuxon.dev>
Commit author: Claudiu Beznea<claudiu.beznea.uj@bp.renesas.com>
Status in newer kernel trees:
6.15.y | Present (exact SHA1)
6.14.y | Present (exact SHA1)
6.12.y | Not found
6.6.y | Not found
6.1.y | Not found
5.15.y | Not found
Note: The patch differs from the upstream commit:
---
1: 5f10170699334 ! 1: b79b1e0e4a210 serial: sh-sci: Clean sci_ports[0] after at earlycon exit
@@ Metadata
## Commit message ##
serial: sh-sci: Clean sci_ports[0] after at earlycon exit
+ commit 5f1017069933489add0c08659673443c9905659e upstream.
+
The early_console_setup() function initializes sci_ports[0].port with an
object of type struct uart_port obtained from the struct earlycon_device
passed as an argument to early_console_setup().
@@ Commit message
Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Link: https://lore.kernel.org/r/20250116182249.3828577-5-claudiu.beznea.uj@bp.renesas.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+ Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
## drivers/tty/serial/sh-sci.c ##
@@ drivers/tty/serial/sh-sci.c: static struct sci_port sci_ports[SCI_NPORTS];
---
Results of testing on various branches:
| Branch | Patch Apply | Build Test |
|---------------------------|-------------|------------|
| stable/linux-5.15.y | Success | Success |
next prev parent reply other threads:[~2025-06-12 2:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 5:00 [PATCH RESEND 5.10.y 0/4] serial: sh-sci: Backport fixes Claudiu
2025-06-11 5:00 ` [PATCH RESEND 5.10.y 1/4] serial: sh-sci: Check if TX data was written to device in .tx_empty() Claudiu
2025-06-12 2:22 ` Sasha Levin
2025-06-11 5:00 ` [PATCH RESEND 5.10.y 2/4] serial: sh-sci: Move runtime PM enable to sci_probe_single() Claudiu
2025-06-12 2:22 ` Sasha Levin
2025-06-11 5:00 ` [PATCH RESEND 5.10.y 3/4] serial: sh-sci: Clean sci_ports[0] after at earlycon exit Claudiu
2025-06-12 2:22 ` Sasha Levin [this message]
2025-06-11 5:00 ` [PATCH RESEND 5.10.y 4/4] serial: sh-sci: Increment the runtime usage counter for the earlycon device Claudiu
2025-06-12 2:22 ` Sasha Levin
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=20250611110644-edcd669842126366@stable.kernel.org \
--to=sashal@kernel.org \
--cc=claudiu.beznea@tuxon.dev \
--cc=stable@vger.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