From: Thierry Reding <thierry.reding@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] pwm: Delete deprecated functions pwm_request() and pwm_free()
Date: Thu, 13 Apr 2023 11:32:07 +0200 [thread overview]
Message-ID: <ZDfMF3wAfbd-1y-Z@orome> (raw)
In-Reply-To: <ZDfLyP5bP0PdBS1J@orome>
[-- Attachment #1: Type: text/plain, Size: 1094 bytes --]
On Thu, Apr 13, 2023 at 11:30:48AM +0200, Thierry Reding wrote:
> On Wed, Apr 12, 2023 at 01:56:36PM +0200, Uwe Kleine-König wrote:
> > Since commit 5a7fbe452ad9 ("backlight: pwm_bl: Drop support for legacy PWM
> > probing") the last user of pwm_request() and pwm_free() is gone. So remove
> > these functions that were deprecated over 10 years ago in commit
> > 8138d2ddbcca ("pwm: Add table-based lookup for static mappings").
> >
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> > ---
> > Documentation/driver-api/pwm.rst | 13 ++++-----
> > drivers/pwm/core.c | 49 --------------------------------
> > include/linux/pwm.h | 13 ---------
> > 3 files changed, 5 insertions(+), 70 deletions(-)
>
> There seem to be two more occurrences of pwm_free() in
> drivers/pwm/core.c, but I think they can trivially be replaced by
> pwm_put(). I can do that while applying, but let me know if you don't
> agree.
I also get warnings about pwm_to_device() now being unused, so I'll
remove that one along with these.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-04-13 9:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-12 11:56 [PATCH] pwm: Delete deprecated functions pwm_request() and pwm_free() Uwe Kleine-König
2023-04-13 9:30 ` Thierry Reding
2023-04-13 9:32 ` Thierry Reding [this message]
2023-04-13 9:34 ` Thierry Reding
2023-04-13 11:38 ` Uwe Kleine-König
2023-04-14 10:43 ` Thierry Reding
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=ZDfMF3wAfbd-1y-Z@orome \
--to=thierry.reding@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-pwm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.