From: Jiri Slaby <jirislaby@kernel.org>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
linux-serial@vger.kernel.org, linux-doc@vger.kernel.org,
netdev@vger.kernel.org
Cc: linux-api@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
"Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Haren Myneni <haren@linux.ibm.com>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Simon Horman <horms@kernel.org>,
Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] tty: synclink_gt: remove broken driver
Date: Thu, 29 Jan 2026 12:41:03 +0100 [thread overview]
Message-ID: <24935907-76b8-4369-a221-f408c9747642@kernel.org> (raw)
In-Reply-To: <20260129075200.38060-1-enelsonmoore@gmail.com>
On 29. 01. 26, 8:51, Ethan Nelson-Moore wrote:
> The synclink_gt driver was marked as broken in commit 426263d5fb40
> ("tty: synclink_gt: mark as BROKEN") in July 2023 because it had severe
> structural problems and there had been no evidence of users since 2016.
> Since then, no meaningful improvements have been made to the driver,
> and it is unlikely that will ever happen due to the lack of interest.
> Drop the driver and references to it in comments and documentation.
Overall, I am all for it, but a few remarks:
> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
> ---
> .../userspace-api/ioctl/ioctl-number.rst | 2 +-
> arch/powerpc/configs/ppc6xx_defconfig | 1 -
> drivers/net/ppp/Kconfig | 4 +-
> drivers/tty/Kconfig | 11 +-
> drivers/tty/Makefile | 1 -
> drivers/tty/n_hdlc.c | 7 -
> drivers/tty/synclink_gt.c | 5038 -----------------
> include/linux/synclink.h | 37 -
vvvvvvvvvvvvvvvvvvvvvvvvvvvvv
> include/uapi/linux/synclink.h | 301 -
Have you checked this is not included in any relevant userspace? How?
Hints: debian code search, github...
> diff --git a/Documentation/userspace-api/ioctl/ioctl-number.rst b/Documentation/userspace-api/ioctl/ioctl-number.rst
> index 7232b3544cec..8abedab9fea7 100644
> --- a/Documentation/userspace-api/ioctl/ioctl-number.rst
> +++ b/Documentation/userspace-api/ioctl/ioctl-number.rst
> @@ -271,7 +271,7 @@ Code Seq# Include File Comments
> 'm' 00-09 linux/mmtimer.h conflict!
> 'm' all linux/mtio.h conflict!
> 'm' all linux/soundcard.h conflict!
> -'m' all linux/synclink.h conflict!
> +'m' all linux/synclink.h Dead since 2026
I would just drop the line, removing one conflicting entry. The letter
is not going to be dead.
Or is this Dead note some ioctl-number's policy?
> --- a/drivers/tty/n_hdlc.c
> +++ b/drivers/tty/n_hdlc.c
> @@ -4,8 +4,6 @@
> * Written by Paul Fulghum paulkf@microgate.com
> * for Microgate Corporation
> *
> - * Microgate and SyncLink are registered trademarks of Microgate Corporation
> - *
> * Adapted from ppp.c, written by Michael Callahan <callahan@maths.ox.ac.uk>,
> * Al Longyear <longyear@netcom.com>,
> * Paul Mackerras <Paul.Mackerras@cs.anu.edu.au>
> @@ -54,11 +52,6 @@
> * this line discipline (or another line discipline that is frame
> * oriented such as N_PPP).
> *
> - * The SyncLink driver (synclink.c) implements both asynchronous
> - * (using standard line discipline N_TTY) and synchronous HDLC
> - * (using N_HDLC) communications, with the latter using the above
> - * conventions.
This paragraph actually talks about long removed synclink.c, removed in:
a1f714b44e34 tty: Remove redundant synclink driver
But OK, let's kick all the remaining traces of synclinks.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2026-01-29 11:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 7:51 [PATCH] tty: synclink_gt: remove broken driver Ethan Nelson-Moore
2026-01-29 11:41 ` Jiri Slaby [this message]
2026-01-30 4:46 ` Ethan Nelson-Moore
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=24935907-76b8-4369-a221-f408c9747642@kernel.org \
--to=jirislaby@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bagasdotme@gmail.com \
--cc=chleroy@kernel.org \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=ebiggers@google.com \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=haren@linux.ibm.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pabeni@redhat.com \
/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