All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thierry Reding <thierry.reding@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Lee Jones <lee.jones@linaro.org>,
	linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] pwm: Drop support for legacy drivers
Date: Wed, 22 Jun 2022 15:33:00 +0200	[thread overview]
Message-ID: <YrMaDKs3GubDfXA5@orome> (raw)
In-Reply-To: <20220521110203.790597-1-u.kleine-koenig@pengutronix.de>

[-- Attachment #1: Type: text/plain, Size: 1086 bytes --]

On Sat, May 21, 2022 at 01:02:03PM +0200, Uwe Kleine-König wrote:
> There are no drivers left providing the legacy callbacks. So drop
> support for these.
> 
> If this commit breaks your out-of-tree pwm driver, look at e.g. commit
> ec00cd5e63f0 ("pwm: renesas-tpu: Implement .apply() callback") for an
> example of the needed conversion for your driver.
> 
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> Hello,
> 
> on top of current Thierry's for-next branch this compiles just fine
> an allmodconfig on arm64, m68k, powerpc, riscv, s390, sparc64 and x86_64
> after cherry-picking 357ad4d89828 ("sound/oss/dmasound: fix
> 'dmasound_setup' defined but not used") to fix an unrelated problem.
> 
> Still I think it would be nice to have this cooking in next for some
> time after the next merge window closes.
> 
> Best regards
> Uwe
> 
>  drivers/pwm/core.c  | 82 +--------------------------------------------
>  include/linux/pwm.h | 12 -------
>  2 files changed, 1 insertion(+), 93 deletions(-)

Applied, thanks.

Thierry

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2022-06-22 13:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 11:02 [PATCH] pwm: Drop support for legacy drivers Uwe Kleine-König
2022-06-19 20:07 ` Uwe Kleine-König
2022-06-22 13:33 ` Thierry Reding [this message]

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=YrMaDKs3GubDfXA5@orome \
    --to=thierry.reding@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=lee.jones@linaro.org \
    --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.