From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linux-kernel@vger.kernel.org, linux-input@vger.kernel.org
Subject: Re: [PATCH 28/47] input: misc: remove blackfin rotary driver
Date: Wed, 14 Mar 2018 09:04:47 -0700 [thread overview]
Message-ID: <20180314160447.GB18065@dtor-ws> (raw)
In-Reply-To: <20180314153603.3127932-29-arnd@arndb.de>
On Wed, Mar 14, 2018 at 04:35:41PM +0100, Arnd Bergmann wrote:
> The blackfin architecture is getting removed, so this
> one is obsolete as well.
>
> Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Please take it through your tree with the rest of bfin removal patches.
> ---
> drivers/input/misc/Kconfig | 9 -
> drivers/input/misc/Makefile | 1 -
> drivers/input/misc/bfin_rotary.c | 294 ------------------------------
> include/linux/platform_data/bfin_rotary.h | 117 ------------
> 4 files changed, 421 deletions(-)
> delete mode 100644 drivers/input/misc/bfin_rotary.c
> delete mode 100644 include/linux/platform_data/bfin_rotary.h
>
> diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig
> index 6a3c753b093b..572b15fa18c2 100644
> --- a/drivers/input/misc/Kconfig
> +++ b/drivers/input/misc/Kconfig
> @@ -655,15 +655,6 @@ config INPUT_DM355EVM
> To compile this driver as a module, choose M here: the
> module will be called dm355evm_keys.
>
> -config INPUT_BFIN_ROTARY
> - tristate "Blackfin Rotary support"
> - depends on BF54x || BF52x
> - help
> - Say Y here if you want to use the Blackfin Rotary.
> -
> - To compile this driver as a module, choose M here: the
> - module will be called bfin-rotary.
> -
> config INPUT_WM831X_ON
> tristate "WM831X ON pin"
> depends on MFD_WM831X
> diff --git a/drivers/input/misc/Makefile b/drivers/input/misc/Makefile
> index 8cc58f362bb8..72cde28649e2 100644
> --- a/drivers/input/misc/Makefile
> +++ b/drivers/input/misc/Makefile
> @@ -19,7 +19,6 @@ obj-$(CONFIG_INPUT_ARIZONA_HAPTICS) += arizona-haptics.o
> obj-$(CONFIG_INPUT_ATI_REMOTE2) += ati_remote2.o
> obj-$(CONFIG_INPUT_ATLAS_BTNS) += atlas_btns.o
> obj-$(CONFIG_INPUT_ATMEL_CAPTOUCH) += atmel_captouch.o
> -obj-$(CONFIG_INPUT_BFIN_ROTARY) += bfin_rotary.o
> obj-$(CONFIG_INPUT_BMA150) += bma150.o
> obj-$(CONFIG_INPUT_CM109) += cm109.o
> obj-$(CONFIG_INPUT_CMA3000) += cma3000_d0x.o
> diff --git a/drivers/input/misc/bfin_rotary.c b/drivers/input/misc/bfin_rotary.c
> deleted file mode 100644
> index 799ce3d2820e..000000000000
> diff --git a/include/linux/platform_data/bfin_rotary.h b/include/linux/platform_data/bfin_rotary.h
> deleted file mode 100644
> index 98829370fee2..000000000000
> --
> 2.9.0
>
--
Dmitry
next prev parent reply other threads:[~2018-03-14 16:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:35 [PATCH 00/47] arch-removal: device drivers Arnd Bergmann
2018-03-14 15:35 ` [PATCH 27/47] input: keyboard: remove bf54x driver Arnd Bergmann
2018-03-14 16:04 ` Dmitry Torokhov
2018-03-14 15:35 ` [PATCH 28/47] input: misc: remove blackfin rotary driver Arnd Bergmann
2018-03-14 16:04 ` Dmitry Torokhov [this message]
2018-03-14 22:45 ` [PATCH 00/47] arch-removal: device drivers Rafael J. Wysocki
2018-03-15 5:32 ` Boris Brezillon
2018-03-15 9:09 ` Arnd Bergmann
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=20180314160447.GB18065@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=arnd@arndb.de \
--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).