From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: linux-pwm@vger.kernel.org, kernel@pengutronix.de
Subject: [PATCH 0/4] pwm patches for the next merge window
Date: Mon, 7 Jan 2019 20:49:35 +0100 [thread overview]
Message-ID: <20190107194938.3004-1-u.kleine-koenig@pengutronix.de> (raw)
Hello,
this is the set of generic pwm patches I already send out before rebased
to v5.0-rc1. I didn't receive any feedback for them but consider patches
1 to 3 ready to apply. For the fourth patch some feedback would be
great.
Uwe Kleine-König (4):
pwm: don't use memcmp to compare struct state variables
pwm: drop per-chip dbg_show callback
pwm: rearrange structures to group members by purpose
[RFC] Documentation: pwm: rework documentation for the framework
Documentation/pwm-sysfs.txt | 44 +++++++
Documentation/pwm.txt | 229 +++++++++++++++---------------------
drivers/pwm/core.c | 10 +-
include/linux/pwm.h | 36 +++---
4 files changed, 161 insertions(+), 158 deletions(-)
create mode 100644 Documentation/pwm-sysfs.txt
--
2.20.1
next reply other threads:[~2019-01-07 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:49 Uwe Kleine-König [this message]
2019-01-07 19:49 ` [PATCH 1/4] pwm: don't use memcmp to compare struct state variables Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 2/4] pwm: drop per-chip dbg_show callback Uwe Kleine-König
2019-01-10 8:36 ` Thierry Reding
2019-01-10 8:52 ` Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 3/4] pwm: rearrange structures to group members by purpose Uwe Kleine-König
2019-01-07 19:49 ` [PATCH 4/4] [RFC] Documentation: pwm: rework documentation for the framework Uwe Kleine-König
2019-07-26 9:39 ` Uwe Kleine-König
2019-09-24 12:00 ` Uwe Kleine-König
2019-01-10 8:35 ` [PATCH 0/4] pwm patches for the next merge window 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=20190107194938.3004-1-u.kleine-koenig@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=linux-pwm@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).