From: Thierry Reding <thierry.reding@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
linux-pwm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] pwm: Fixes for v6.3-rc6
Date: Thu, 6 Apr 2023 15:00:55 +0200 [thread overview]
Message-ID: <20230406130055.1244344-1-thierry.reding@gmail.com> (raw)
Hi Linus,
The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git tags/pwm/for-6.3-rc6
for you to fetch changes up to 1271a7b98e7989ba6bb978e14403fc84efe16e13:
pwm: Zero-initialize the pwm_state passed to driver's .get_state() (2023-03-23 14:44:43 +0100)
Thanks,
Thierry
----------------------------------------------------------------
pwm: Fixes for v6.3-rc6
These are some fixes to make sure the PWM state structure is always
initialized to a known state. Prior to this it could happen in some
situations that random data from the stack would leak into the data
structure and cause subtle bugs.
----------------------------------------------------------------
Uwe Kleine-König (6):
pwm: hibvt: Explicitly set .polarity in .get_state()
pwm: cros-ec: Explicitly set .polarity in .get_state()
pwm: iqs620a: Explicitly set .polarity in .get_state()
pwm: sprd: Explicitly set .polarity in .get_state()
pwm: meson: Explicitly set .polarity in .get_state()
pwm: Zero-initialize the pwm_state passed to driver's .get_state()
drivers/pwm/core.c | 12 ++++++++++--
drivers/pwm/pwm-cros-ec.c | 1 +
drivers/pwm/pwm-hibvt.c | 1 +
drivers/pwm/pwm-iqs620a.c | 1 +
drivers/pwm/pwm-meson.c | 8 ++++++++
drivers/pwm/pwm-sprd.c | 1 +
6 files changed, 22 insertions(+), 2 deletions(-)
next reply other threads:[~2023-04-06 13:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 13:00 Thierry Reding [this message]
2023-04-06 18:46 ` 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=20230406130055.1244344-1-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--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®