From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: "Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lee Jones" <lee@kernel.org>,
linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
linux-leds@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-fbdev@vger.kernel.org
Cc: Jonathan Cameron <jic23@kernel.org>,
Lars-Peter Clausen <lars@metafoo.de>, Pavel Machek <pavel@ucw.cz>,
Daniel Thompson <daniel.thompson@linaro.org>,
Jingoo Han <jingoohan1@gmail.com>, Helge Deller <deller@gmx.de>,
Johan Hovold <jhovold@gmail.com>,
Linus Walleij <linus.walleij@linaro.org>
Subject: [PATCH v1 0/4] lm3533: Remove the outdated drivers
Date: Fri, 31 May 2024 19:56:12 +0300 [thread overview]
Message-ID: <20240531170844.1595468-1-andriy.shevchenko@linux.intel.com> (raw)
Driver is quite outdated from the Linux kernel internal APIs
perspective. In particular GPIO code is using legacy calls,
that started being replaced by a new API ca. 2014, i.e. ten
years ago.
Suggested-by: Linus Walleij <linus.walleij@linaro.org>
Andy Shevchenko (4):
backlight: lm3533_bl: Remove the driver
iio: light: lm3533-als: Remove the driver
leds: lm3533: Remove the driver
mfd: lm3533: Remove the driver
drivers/iio/light/Kconfig | 17 -
drivers/iio/light/Makefile | 1 -
drivers/iio/light/lm3533-als.c | 922 ----------------------------
drivers/leds/Kconfig | 13 -
drivers/leds/Makefile | 1 -
drivers/leds/leds-lm3533.c | 755 -----------------------
drivers/mfd/lm3533-core.c | 645 -------------------
drivers/video/backlight/Kconfig | 11 -
drivers/video/backlight/Makefile | 1 -
drivers/video/backlight/lm3533_bl.c | 399 ------------
include/linux/mfd/lm3533.h | 100 ---
11 files changed, 2865 deletions(-)
delete mode 100644 drivers/iio/light/lm3533-als.c
delete mode 100644 drivers/leds/leds-lm3533.c
delete mode 100644 drivers/mfd/lm3533-core.c
delete mode 100644 drivers/video/backlight/lm3533_bl.c
delete mode 100644 include/linux/mfd/lm3533.h
--
2.43.0.rc1.1336.g36b5255a03ac
next reply other threads:[~2024-05-31 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 16:56 Andy Shevchenko [this message]
2024-05-31 16:56 ` [PATCH v1 1/4] backlight: lm3533_bl: Remove the driver Andy Shevchenko
2024-05-31 16:56 ` [PATCH v1 2/4] iio: light: lm3533-als: " Andy Shevchenko
2024-06-01 13:05 ` Jonathan Cameron
2024-06-02 9:46 ` Andy Shevchenko
2024-05-31 16:56 ` [PATCH v1 3/4] leds: lm3533: " Andy Shevchenko
2024-05-31 16:56 ` [PATCH v1 4/4] mfd: " Andy Shevchenko
2024-06-01 0:27 ` kernel test robot
2024-06-01 2:31 ` kernel test robot
2024-05-31 17:14 ` [PATCH v1 0/4] lm3533: Remove the outdated drivers Lee Jones
2024-05-31 17:17 ` Andy Shevchenko
2024-05-31 17:14 ` Andy Shevchenko
2024-05-31 17:15 ` Lee Jones
2024-05-31 17:37 ` Andy Shevchenko
2024-05-31 17:17 ` Andy Shevchenko
2024-06-05 12:42 ` Johan Hovold
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=20240531170844.1595468-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=daniel.thompson@linaro.org \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=jhovold@gmail.com \
--cc=jic23@kernel.org \
--cc=jingoohan1@gmail.com \
--cc=lars@metafoo.de \
--cc=lee@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=u.kleine-koenig@pengutronix.de \
/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).