From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Henk Vergonet <Henk.Vergonet@gmail.com>,
Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <bentiss@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 <chleroy@kernel.org>
Cc: Oliver Neukum <oneukum@suse.com>, Martin Diehl <m-diehl@gmx.de>,
"Alfred E . Heggestad" <aeh@db.org>,
Thomas Reitmayr <treitmayr@devbase.at>,
Slawomir Stepien <sst@poczta.fm>, Jie Wang <jie.wang@intel.com>,
Manuel Ebner <manuelebnerli@mailbox.org>,
Randy Dunlap <rdunlap@infradead.org>,
usbb2k-api-dev@nongnu.org, linux-input@vger.kernel.org,
linux-usb@vger.kernel.org, linux-doc@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Input: remove obsolete yealink USB phone driver
Date: Wed, 11 Nov 2026 13:57:21 -0800 [thread overview]
Message-ID: <20261111215723.3802209-1-dmitry.torokhov@gmail.com> (raw)
This short series removes the obsolete yealink driver for the mid-2000s
Yealink USB-P1K (0x6993:0xb001) USB 1.1 Skype/VoIP telephone handset
and drops its module selection from ppc6xx_defconfig.
The hardware relied on dedicated userspace bridge utilities (such as
usbb2k-api / kb2kskype for the defunct legacy Skype desktop API, or
yeaphone for liblinphone) to drive its keypad, segmented LCD, and tones
through custom sysfs attributes. That userspace ecosystem has been
unmaintained for over 15 years, and the driver itself has seen no
functional updates, hardware testing, or new device IDs since 2008
while continuing to attract syzbot USB fuzzing reports and drive-by
cleanup patches.
Thanks.
Dmitry Torokhov (2):
powerpc/configs: drop CONFIG_INPUT_YEALINK from ppc6xx_defconfig
Input: yealink - remove driver
Documentation/.renames.txt | 1 -
Documentation/input/devices/yealink.rst | 226 ------
MAINTAINERS | 6 -
arch/powerpc/configs/ppc6xx_defconfig | 1 -
drivers/hid/hid-ids.h | 3 -
drivers/hid/hid-quirks.c | 1 -
drivers/input/misc/Kconfig | 15 -
drivers/input/misc/Makefile | 1 -
drivers/input/misc/yealink.c | 950 ------------------------
drivers/input/misc/yealink.h | 206 -----
10 files changed, 1410 deletions(-)
delete mode 100644 Documentation/input/devices/yealink.rst
delete mode 100644 drivers/input/misc/yealink.c
delete mode 100644 drivers/input/misc/yealink.h
--
2.56.0.567.gdb80ae8cd5-goog
next reply other threads:[~2026-11-11 21:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 21:57 Dmitry Torokhov [this message]
2026-11-11 21:57 ` [PATCH 1/2] powerpc/configs: drop CONFIG_INPUT_YEALINK from ppc6xx_defconfig Dmitry Torokhov
2026-11-11 21:57 ` [PATCH 2/2] Input: yealink - remove driver Dmitry Torokhov
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=20261111215723.3802209-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=Henk.Vergonet@gmail.com \
--cc=aeh@db.org \
--cc=bentiss@kernel.org \
--cc=chleroy@kernel.org \
--cc=corbet@lwn.net \
--cc=jie.wang@intel.com \
--cc=jikos@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=m-diehl@gmx.de \
--cc=maddy@linux.ibm.com \
--cc=manuelebnerli@mailbox.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=oneukum@suse.com \
--cc=rdunlap@infradead.org \
--cc=sst@poczta.fm \
--cc=treitmayr@devbase.at \
--cc=usbb2k-api-dev@nongnu.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
all inboxes | Powered by JetHome®