From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.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] TTY/Serial driver fixes for 6.8-rc3
Date: Sat, 3 Feb 2024 13:49:41 -0800 [thread overview]
Message-ID: <Zb609YTmtyjUEwhc@kroah.com> (raw)
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:
Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-6.8-rc3
for you to fetch changes up to b35f8dbbce818b02c730dc85133dc7754266e084:
serial: max310x: prevent infinite while() loop in port startup (2024-01-27 19:09:10 -0800)
----------------------------------------------------------------
TTY/Serial driver fixes for 6.8-rc3
Here are some small tty and serial driver fixes for 6.8-rc3 that resolve
a number of reported issues. Included in here are:
- rs485 flag definition fix that affected the user/kernel abi in -rc1
- max310x driver fixes
- 8250_pci1xxxx driver off-by-one fix
- uart_tiocmget locking race fix
All of these have been in linux-next for over a week with no reported
issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Christoph Niedermaier (1):
tty: serial: Fix bit order in RS485 flag definitions
Dan Carpenter (1):
serial: 8250_pci1xxxx: fix off by one in pci1xxxx_process_read_data()
Gui-Dong Han (1):
serial: core: Fix atomicity violation in uart_tiocmget
Hugo Villeneuve (4):
serial: max310x: set default value when reading clock ready bit
serial: max310x: improve crystal stable clock detection
serial: max310x: fail probe if clock crystal is unstable
serial: max310x: prevent infinite while() loop in port startup
drivers/tty/serial/8250/8250_pci1xxxx.c | 4 +--
drivers/tty/serial/max310x.c | 53 ++++++++++++++++++++++++++-------
drivers/tty/serial/serial_core.c | 2 +-
include/uapi/linux/serial.h | 13 ++++----
4 files changed, 53 insertions(+), 19 deletions(-)
next reply other threads:[~2024-02-03 21:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-03 21:49 Greg KH [this message]
2024-02-04 7:18 ` [GIT PULL] TTY/Serial driver fixes for 6.8-rc3 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=Zb609YTmtyjUEwhc@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=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