From: "Arnd Bergmann" <arnd@arndb.de>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Linus Walleij" <linus.walleij@linaro.org>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
"Lee Jones" <lee@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] Input: keypad-nomadik-ske - remove the driver
Date: Mon, 19 Aug 2024 11:29:32 +0200 [thread overview]
Message-ID: <1bc01e00-7b70-4e90-8060-f3de3ec7afa3@app.fastmail.com> (raw)
In-Reply-To: <Zr-gX0dfN4te_8VG@google.com>
On Fri, Aug 16, 2024, at 20:54, Dmitry Torokhov wrote:
> The users of this driver were removed in 2013 in commit 28633c54bda6
> ("ARM: ux500: Rip out keypad initialisation which is no longer used").
>
> Remove the driver as well.
>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> drivers/input/keyboard/Kconfig | 11 -
> drivers/input/keyboard/Makefile | 1 -
> drivers/input/keyboard/nomadik-ske-keypad.c | 378 ------------------
> .../linux/platform_data/keypad-nomadik-ske.h | 50 ---
> 4 files changed, 440 deletions(-)
>
Acked-by: Arnd Bergmann <arnd@arndb.de>
I have a list of drivers that I determined to be likely
unused as well and found a few more input drivers
that were unused in 2022:
CONFIG_KEYBOARD_ADP5520/CONFIG_PMIC_ADP5520
CONFIG_KEYBOARD_ADP5589
CONFIG_INPUT_AD714X
CONFIG_TOUCHSCREEN_AD7877
As far as I can tell, these all lost their last device
definition, or they never had one and are impossible to
be used with device tree data.
Arnd
next prev parent reply other threads:[~2024-08-19 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 18:54 [PATCH] Input: keypad-nomadik-ske - remove the driver Dmitry Torokhov
2024-08-19 9:29 ` Arnd Bergmann [this message]
2024-08-19 14:54 ` Dmitry Torokhov
2024-08-27 9:52 ` Hennerich, Michael
2024-09-06 8:38 ` Nuno Sá
2024-09-06 16:51 ` Dmitry Torokhov
2024-09-09 10:34 ` Nuno Sá
2024-08-24 14:35 ` Linus Walleij
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=1bc01e00-7b70-4e90-8060-f3de3ec7afa3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=dmitry.torokhov@gmail.com \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).