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 0/4] pwm patches for the next merge window
Date: Thu, 10 Jan 2019 09:35:50 +0100 [thread overview]
Message-ID: <20190110083550.GE5213@ulmo> (raw)
In-Reply-To: <20190107194938.3004-1-u.kleine-koenig@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 385 bytes --]
On Mon, Jan 07, 2019 at 08:49:35PM +0100, Uwe Kleine-König wrote:
> 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.
Patches 1-3 applied, will take a closer look at patch 4.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-01-10 8:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 19:49 [PATCH 0/4] pwm patches for the next merge window Uwe Kleine-König
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 ` 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=20190110083550.GE5213@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.