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 fix for 6.17-rc1
Date: Sat, 9 Aug 2025 16:48:50 +0200 [thread overview]
Message-ID: <aJdf0rAZ5x5klUhX@kroah.com> (raw)
The following changes since commit 89748acdf226fd1a8775ff6fa2703f8412b286c8:
Merge tag 'drm-next-2025-08-01' of https://gitlab.freedesktop.org/drm/kernel (2025-07-31 21:47:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git tags/tty-6.16-rc1-2
for you to fetch changes up to 55a984928bfa30c7877e28f16910e6de1c170f1f:
Revert "tty: vt: use _IO() to define ioctl numbers" (2025-08-01 10:42:22 +0200)
----------------------------------------------------------------
TTY revert fix for 6.16-rc1
Here is a single revert of one of the previous patches that went in the
last tty/serial merge that is breaking userspace on some platforms
(specifically powerpc, probably a few others.) It accidentially changed
the ioctl values of some tty ioctls, which breaks xorg.
The revert has been in linux-next all this week with no reported issues.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
----------------------------------------------------------------
Jiri Slaby (SUSE) (1):
Revert "tty: vt: use _IO() to define ioctl numbers"
include/uapi/linux/vt.h | 34 +++++++++++++++++-----------------
1 file changed, 17 insertions(+), 17 deletions(-)
next reply other threads:[~2025-08-09 14:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-09 14:48 Greg KH [this message]
2025-08-09 14:57 ` [GIT PULL] TTY / Serial driver fix for 6.17-rc1 Greg KH
2025-08-09 15:18 ` Linus Torvalds
2025-08-10 15:24 ` Greg KH
2025-08-09 15:20 ` 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=aJdf0rAZ5x5klUhX@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 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.