From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Lee Jones" <lee.jones@linaro.org>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] pwm: Fixes for v5.14-rc2
Date: Wed, 14 Jul 2021 09:43:26 +0200 [thread overview]
Message-ID: <20210714074326.89692-1-thierry.reding@gmail.com> (raw)
Hi Linus,
The following changes since commit bebedf2bb4a9e0cb4ffa72cbc960728051b338a4:
pwm: Remove redundant assignment to pointer pwm (2021-07-07 21:43:32 +0200)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git tags/pwm/for-5.14-rc2
for you to fetch changes up to f4a8e31ed84ec646c158824f423cb22d1f362bbf:
pwm: ep93xx: Ensure configuring period and duty_cycle isn't wrongly skipped (2021-07-08 16:09:30 +0200)
Thanks,
Thierry
----------------------------------------------------------------
pwm: Fixes for v5.14-rc2
This contains a couple of fixes from Uwe that I missed for v5.14-rc1.
----------------------------------------------------------------
Uwe Kleine-König (5):
pwm: sprd: Ensure configuring period and duty_cycle isn't wrongly skipped
pwm: spear: Ensure configuring period and duty_cycle isn't wrongly skipped
pwm: tiecap: Ensure configuring period and duty_cycle isn't wrongly skipped
pwm: berlin: Ensure configuring period and duty_cycle isn't wrongly skipped
pwm: ep93xx: Ensure configuring period and duty_cycle isn't wrongly skipped
drivers/pwm/pwm-berlin.c | 9 ++---
drivers/pwm/pwm-ep93xx.c | 85 +++++++++++++++++++++++-------------------------
drivers/pwm/pwm-spear.c | 9 ++---
drivers/pwm/pwm-sprd.c | 11 +++----
drivers/pwm/pwm-tiecap.c | 15 ++++-----
5 files changed, 56 insertions(+), 73 deletions(-)
next reply other threads:[~2021-07-14 7:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-14 7:43 Thierry Reding [this message]
2021-07-16 1:13 ` pr-tracker-bot
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=20210714074326.89692-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®