From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [GIT PULL] Serial driver fixes for 6.13-rc7
Date: Sun, 12 Jan 2025 15:05:29 +0100 [thread overview]
Message-ID: <Z4PMKaKtcsI_zmU4@kroah.com> (raw)
The following changes since commit 78d4f34e2115b517bcbfe7ec0d018bbbb6f9b0b8:
Linux 6.13-rc3 (2024-12-15 15:58:23 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-6.13-rc7
for you to fetch changes up to 0cfc36ea51684b5932cd3951ded523777d807af2:
serial: stm32: use port lock wrappers for break control (2024-12-23 19:01:54 +0100)
----------------------------------------------------------------
Serial driver fixes for 6.13-rc7
Here are 3 small serial driver fixes tree. They resolve some reported
issues:
- stm32 break control fix
- 8250 runtime pm usage counter fix
- imx driver locking fix.
All have been in my tree and linux-next for 3 weeks now, with no
reported issues:
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Ben Wolsieffer (1):
serial: stm32: use port lock wrappers for break control
Ilpo Järvinen (1):
tty: serial: 8250: Fix another runtime PM usage counter underflow
Xiaolei Wang (1):
serial: imx: Use uart_port_lock_irq() instead of uart_port_lock()
drivers/tty/serial/8250/8250_core.c | 3 +++
drivers/tty/serial/imx.c | 4 ++--
drivers/tty/serial/stm32-usart.c | 4 ++--
3 files changed, 7 insertions(+), 4 deletions(-)
next reply other threads:[~2025-01-12 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-12 14:05 Greg KH [this message]
2025-01-12 22:36 ` [GIT PULL] Serial driver fixes for 6.13-rc7 pr-tracker-bot
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=Z4PMKaKtcsI_zmU4@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=geert@linux-m68k.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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