From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>,
Lee Jones <lee.jones@linaro.org>
Cc: Shawn Guo <shawnguo@kernel.org>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
linux-pwm@vger.kernel.org
Subject: [PATCH 0/2] Changes for pwmchip_remove()
Date: Wed, 24 Mar 2021 16:20:56 +0100 [thread overview]
Message-ID: <20210324152058.69022-1-u.kleine-koenig@pengutronix.de> (raw)
pwmchip_remove currently can (theoretically) return an error code and
most drivers check for that and pass an error to the upper layer just to
be ignored there. Before device links were used this resulted in
half-registered drivers that failed to free all allocated resources.
Today it just makes these remove functions more complicated than
necessary.
This series simplifies pwmchip_remove() and prepares a first driver to
eventually make pwmchip_remove() return void.
Best regards
Uwe
Uwe Kleine-König (2):
pwm: Drop unused error path from pwmchip_remove()
pwm: imx27: Don't check the return code of pwmchip_remove()
drivers/pwm/core.c | 16 ++--------------
drivers/pwm/pwm-imx27.c | 4 +++-
2 files changed, 5 insertions(+), 15 deletions(-)
--
2.30.2
next reply other threads:[~2021-03-24 15:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 15:20 Uwe Kleine-König [this message]
2021-03-24 15:20 ` [PATCH 1/2] pwm: Drop unused error path from pwmchip_remove() Uwe Kleine-König
2021-04-09 11:57 ` Thierry Reding
2021-04-10 21:56 ` Uwe Kleine-König
2021-03-24 15:20 ` [PATCH 2/2] pwm: imx27: Don't check the return code of pwmchip_remove() Uwe Kleine-König
2021-04-09 12:00 ` Thierry Reding
2021-05-25 19:59 ` Uwe Kleine-König
2021-07-05 13:15 ` Uwe Kleine-König
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=20210324152058.69022-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-imx@nxp.com \
--cc=linux-pwm@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=thierry.reding@gmail.com \
/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).