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 5.10.y 2/4] serial: sh-sci: Move runtime PM enable to sci_probe_single()
Date: Tue, 3 Jun 2025 14:36:03 -0400 [thread overview]
Message-ID: <20250603142332-ed8dd7bfa3407463@stable.kernel.org> (raw)
In-Reply-To: <20250603093701.3928327-3-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: 239f11209e5f282e16f5241b99256e25dd0614b6
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: 239f11209e5f2 ! 1: ef2e932fb64e7 serial: sh-sci: Move runtime PM enable to sci_probe_single()
@@ Metadata
## Commit message ##
serial: sh-sci: Move runtime PM enable to sci_probe_single()
+ commit 239f11209e5f282e16f5241b99256e25dd0614b6 upstream.
+
Relocate the runtime PM enable operation to sci_probe_single(). This change
prepares the codebase for upcoming fixes.
@@ Commit message
Signed-off-by: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Link: https://lore.kernel.org/r/20250116182249.3828577-3-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 int sci_init_single(struct platform_device *dev,
@@ drivers/tty/serial/sh-sci.c: static int sci_init_single(struct platform_device *
-
#if defined(CONFIG_SERIAL_SH_SCI_CONSOLE) || \
defined(CONFIG_SERIAL_SH_SCI_EARLYCON)
- static void serial_console_putchar(struct uart_port *port, unsigned char ch)
-@@ drivers/tty/serial/sh-sci.c: static void sci_remove(struct platform_device *dev)
+ static void serial_console_putchar(struct uart_port *port, int ch)
+@@ drivers/tty/serial/sh-sci.c: static int sci_remove(struct platform_device *dev)
sci_ports_in_use &= ~BIT(port->port.line);
uart_remove_one_port(&sci_uart_driver, &port->port);
---
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-03 18:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 9:36 [PATCH 5.10.y 0/4] serial: sh-sci: Backport fixes Claudiu
2025-06-03 9:36 ` [PATCH 5.10.y 1/4] serial: sh-sci: Check if TX data was written to device in .tx_empty() Claudiu
2025-06-03 19:04 ` Sasha Levin
2025-06-04 13:27 ` Greg KH
2025-06-03 9:36 ` [PATCH 5.10.y 2/4] serial: sh-sci: Move runtime PM enable to sci_probe_single() Claudiu
2025-06-03 18:36 ` Sasha Levin [this message]
2025-06-03 9:37 ` [PATCH 5.10.y 3/4] serial: sh-sci: Clean sci_ports[0] after at earlycon exit Claudiu
2025-06-03 18:35 ` Sasha Levin
2025-06-03 9:37 ` [PATCH 5.10.y 4/4] serial: sh-sci: Increment the runtime usage counter for the earlycon device Claudiu
2025-06-03 18:36 ` 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=20250603142332-ed8dd7bfa3407463@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 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.