public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Jiri Slaby <jslaby@suse.cz>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [GIT PULL] TTY/Serial driver fixes for 7.0-rc5
Date: Fri, 20 Mar 2026 18:26:02 +0100	[thread overview]
Message-ID: <ab2DKnELM8LPfew8@kroah.com> (raw)

The following changes since commit 1f318b96cc84d7c2ab792fcc0bfd42a7ca890681:

  Linux 7.0-rc3 (2026-03-08 16:56:54 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-7.0-rc5

for you to fetch changes up to 5eb608319bb56464674a71b4a66ea65c6c435d64:

  vt: save/restore unicode screen buffer for alternate screen (2026-03-13 09:15:58 +0100)

----------------------------------------------------------------
TTY/Serial fixes for 7.0-rc5

Here are some small tty/vt and serial driver fixes for 7.0-rc5.
Included in here are:
  - 8250 driver fixes for reported problems
  - serial core lockup fix
  - uartlite driver bugfix
  - vt save/restore bugfix

All of these have been in linux-next for over a week with no reported
problems.

Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

----------------------------------------------------------------
Ilpo Järvinen (7):
      serial: 8250: Protect LCR write in shutdown
      serial: 8250_dw: Avoid unnecessary LCR writes
      serial: 8250: Add serial8250_handle_irq_locked()
      serial: 8250_dw: Rework dw8250_handle_irq() locking and IIR handling
      serial: 8250_dw: Rework IIR_NO_INT handling to stop interrupt storm
      serial: 8250: Add late synchronize_irq() to shutdown to handle DW UART BUSY
      serial: 8250_dw: Ensure BUSY is deasserted

Jiayuan Chen (1):
      serial: core: fix infinite loop in handle_tx() for PORT_UNKNOWN

Maciej Andrzejewski ICEYE (1):
      serial: uartlite: fix PM runtime usage count underflow on probe

Martin Roukala (né Peres) (1):
      serial: 8250_pci: add support for the AX99100

Nicolas Pitre (1):
      vt: save/restore unicode screen buffer for alternate screen

Peng Zhang (1):
      serial: 8250: always disable IRQ during THRE test

Raul E Rangel (1):
      serial: 8250: Fix TX deadlock when using DMA

 drivers/tty/serial/8250/8250.h      |  25 +++
 drivers/tty/serial/8250/8250_dma.c  |  15 ++
 drivers/tty/serial/8250/8250_dw.c   | 304 ++++++++++++++++++++++++++++--------
 drivers/tty/serial/8250/8250_pci.c  |  17 ++
 drivers/tty/serial/8250/8250_port.c |  75 +++++----
 drivers/tty/serial/serial_core.c    |   5 +-
 drivers/tty/serial/uartlite.c       |   1 +
 drivers/tty/vt/vt.c                 |   8 +
 include/linux/console_struct.h      |   1 +
 include/linux/serial_8250.h         |   1 +
 10 files changed, 356 insertions(+), 96 deletions(-)

             reply	other threads:[~2026-03-20 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20 17:26 Greg KH [this message]
2026-03-20 19:12 ` [GIT PULL] TTY/Serial driver fixes for 7.0-rc5 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=ab2DKnELM8LPfew8@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --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