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 5.7-rc3
Date: Sun, 26 Apr 2020 12:48:42 +0200 [thread overview]
Message-ID: <20200426104842.GA2121011@kroah.com> (raw)
The following changes since commit 8f3d9f354286745c751374f5f1fcafee6b3f3136:
Linux 5.7-rc1 (2020-04-12 12:35:55 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-5.7-rc3
for you to fetch changes up to 9a9fc42b86c06120744555fea43fdcabe297c656:
tty: hvc: fix buffer overflow during hvc_alloc(). (2020-04-23 16:02:07 +0200)
----------------------------------------------------------------
TTY/Serial fixes for 5.7-rc3
Here are some tty and serial driver fixes for 5.7-rc3.
The "largest" in here are a number of reverts for previous changes to
the uartps serial driver that turned out to not be a good idea at all.
The others are just small fixes found by people and tools. Included in
here is a much-reported symbol export needed by previous changes that
happened in 5.7-rc1. All of these have been in linux-next for a while
with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Amit Singh Tomar (1):
tty: serial: owl: add "much needed" clk_prepare_enable()
Andrew Melnychenko (1):
tty: hvc: fix buffer overflow during hvc_alloc().
Andy Shevchenko (1):
serial: sunhv: Initialize lock for non-registered console
Dmitry Safonov (1):
tty/sysrq: Export sysrq_mask(), sysrq_toggle_support()
Jiri Slaby (1):
tty: rocket, avoid OOB access
Kazuhiro Fujita (1):
serial: sh-sci: Make sure status register SCxSR is read in correct sequence
Michal Simek (7):
Revert "serial: uartps: Fix uartps_major handling"
Revert "serial: uartps: Use the same dynamic major number for all ports"
Revert "serial: uartps: Fix error path when alloc failed"
Revert "serial: uartps: Do not allow use aliases >= MAX_UART_INSTANCES"
Revert "serial: uartps: Change uart ID port allocation"
Revert "serial: uartps: Move Port ID to device data structure"
Revert "serial: uartps: Register own uart console and driver structures"
Nicolas Pitre (2):
vt: don't use kmalloc() for the unicode screen buffer
vt: don't hardcode the mem allocation upper bound
Zou Wei (1):
tty: serial: bcm63xx: fix missing clk_put() in bcm63xx_uart
drivers/tty/hvc/hvc_console.c | 23 ++--
drivers/tty/rocket.c | 25 +++--
drivers/tty/serial/bcm63xx_uart.c | 4 +-
drivers/tty/serial/owl-uart.c | 7 ++
drivers/tty/serial/sh-sci.c | 13 ++-
drivers/tty/serial/sunhv.c | 3 +
drivers/tty/serial/xilinx_uartps.c | 211 +++++++++----------------------------
drivers/tty/sysrq.c | 2 +
drivers/tty/vt/vt.c | 7 +-
9 files changed, 106 insertions(+), 189 deletions(-)
next reply other threads:[~2020-04-26 10:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-26 10:48 Greg KH [this message]
2020-04-26 18:25 ` 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=20200426104842.GA2121011@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
Powered by JetHome