From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Wolfram Sang <wsa@kernel.org>, Arnd Bergmann <arnd@arndb.de>
Cc: Felipe Balbi <balbi@kernel.org>, Tony Lindgren <tony@atomide.com>,
Hyunjung Ko <hj351016@gmail.com>,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Input: remove unused lm8323 and lm8333 keypad drivers
Date: Sun, 8 Nov 2026 23:29:48 -0800 [thread overview]
Message-ID: <20261109072950.3474308-1-dmitry.torokhov@gmail.com> (raw)
Both the LM8323 and LM8333 keypad drivers strictly require legacy
platform data, lack Device Tree or generic device property support, and
have no users in mainline.
Follow up on the earlier mailing list inquiry [1] (where Wolfram Sang
confirmed that LM8333 can be dropped and no objections were raised for
either driver) and remove both drivers along with their platform data
headers.
[1] https://lore.kernel.org/r/Zr6I9RB5mibU_12N@google.com
Thanks.
Dmitry Torokhov (2):
Input: lm8323 - remove driver
Input: lm8333 - remove driver
drivers/input/keyboard/Kconfig | 22 -
drivers/input/keyboard/Makefile | 2 -
drivers/input/keyboard/lm8323.c | 813 ---------------------------
drivers/input/keyboard/lm8333.c | 213 -------
include/linux/input/lm8333.h | 24 -
include/linux/platform_data/lm8323.h | 34 --
6 files changed, 1108 deletions(-)
delete mode 100644 drivers/input/keyboard/lm8323.c
delete mode 100644 drivers/input/keyboard/lm8333.c
delete mode 100644 include/linux/input/lm8333.h
delete mode 100644 include/linux/platform_data/lm8323.h
--
2.56.0.506.g506a7eabc5-goog
next reply other threads:[~2026-11-09 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-09 7:29 Dmitry Torokhov [this message]
2026-11-09 7:29 ` [PATCH 1/2] Input: lm8323 - remove driver Dmitry Torokhov
2026-11-09 7:46 ` khj
2026-11-09 7:53 ` Arnd Bergmann
2026-11-09 8:01 ` Dmitry Torokhov
2026-11-09 7:29 ` [PATCH 2/2] Input: lm8333 " 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=20261109072950.3474308-1-dmitry.torokhov@gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@arndb.de \
--cc=balbi@kernel.org \
--cc=hj351016@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.com \
--cc=wsa@kernel.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®