[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20230113182427.257484-1-u.kleine-koenig@pengutronix.de>
Date: Fri, 13 Jan 2023 19:24:25 +0100
From: Uwe Kleine-König
<u.kleine-koenig@...gutronix.de>
To: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@....cz>
Cc: linux-kernel@...r.kernel.org, kernel@...gutronix.de,
linux-leds@...r.kernel.org
Subject: [PATCH 0/2] mfd: Make .disable() callback and mfd_cell_disable() return void
Hello,
this series eventually changes mfd_cell_disable() to return void. Before it
returned an int and always 0. The motivation is to not force drivers to do
error handling that is never hit. Here only a single driver did that:
leds-asic3. For that driver this is a nice improvement because a platform
driver's remove callback is not supposed to return an error code.
This serves as a preparation for the quest to make struct
platform_driver::remove return void, too.
This series is build-tested (using allmodconfig) on arm64, m68k, powerpc,
riscv, s390, sparc64 and x86_64.
I suggest to let this series go into mainline via the mfd tree. So an Ack by
Pavel for the led bits would be nice to let Lee pick it up in good conscience.
Best regards
Uwe
Uwe Kleine-König (2):
mfd: Make .disable() callback return void
mfd: Make mfd_cell_disable() return void
drivers/leds/leds-asic3.c | 6 ++++--
drivers/mfd/asic3.c | 17 +++++++++--------
drivers/mfd/htc-pasic3.c | 3 +--
drivers/mfd/mfd-core.c | 10 ++++------
drivers/mfd/t7l66xb.c | 4 +---
drivers/mfd/tc6387xb.c | 4 +---
drivers/mfd/tc6393xb.c | 16 ++++++++++------
include/linux/mfd/core.h | 4 ++--
8 files changed, 32 insertions(+), 32 deletions(-)
base-commit: 1b929c02afd37871d5afb9d498426f83432e71c2
--
2.39.0
Powered by blists - more mailing lists