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 1/3] MAINTAINERS: add a selection of pwm related keywords to the PWM entry
Date: Tue, 24 Sep 2019 13:03:26 +0200 [thread overview]
Message-ID: <20190924110326.GG14924@ulmo> (raw)
In-Reply-To: <20190923084937.20358-1-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 977 bytes --]
On Mon, Sep 23, 2019 at 10:49:35AM +0200, Uwe Kleine-König wrote:
> This is just a small subset of the relevant functions, but should at
> least catch all new code as every consumer has to call pwm_apply_state
> (or the legacy function pwm_config) and every PWM provider has to
> implement pwm_ops.
>
> Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
All three patches applied. Thanks for volunteering to be a reviewer!
Thierry
> diff --git a/MAINTAINERS b/MAINTAINERS
> index b85f2abfe69b..2e8dd2ea4eaa 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -13254,6 +13254,7 @@ F: drivers/video/backlight/pwm_bl.c
> F: include/linux/pwm_backlight.h
> F: drivers/gpio/gpio-mvebu.c
> F: Documentation/devicetree/bindings/gpio/gpio-mvebu.txt
> +K: pwm_(config|apply_state|ops)
>
> PXA GPIO DRIVER
> M: Robert Jarzmik <robert.jarzmik@free.fr>
> --
> 2.23.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-09-24 11:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-23 8:49 [PATCH 1/3] MAINTAINERS: add a selection of pwm related keywords to the PWM entry Uwe Kleine-König
2019-09-23 8:49 ` [PATCH 2/3] MAINTAINERS: Add patchwork link for " Uwe Kleine-König
2019-09-23 8:49 ` [PATCH 3/3] MAINTAINERS: Add myself as reviewer for the PWM subsystem Uwe Kleine-König
2019-09-24 11:03 ` 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=20190924110326.GG14924@ulmo \
--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.