From: Ilkka Koskinen <ilkka.koskinen@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Thierry Reding <thierry.reding@gmail.com>,
linux-pwm@vger.kernel.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH v2 0/4] pwm: lpss: clean up series
Date: Thu, 5 Jan 2017 00:09:19 -0800 [thread overview]
Message-ID: <20170105080919.GA45669@kammari> (raw)
In-Reply-To: <20170102091647.86910-1-andriy.shevchenko@linux.intel.com>
On Mon, Jan 02, 2017 at 11:16:43AM +0200, Andy Shevchenko wrote:
> There are clean ups and switch to new atomic API (would be considered as an
> improvement).
>
> The series tested on various Intel platforms, such as Edison and Minnowboard
> MAX.
>
> And the part I like most is -2 lines statistics!
>
> Thierry, what should we do to get this series in? It was already more than 2
> months of waiting for response from you. Two pings went to black hole.
> So, Cc'ing to Linus directly this time, sorry.
>
> Since v1:
> - rebase on top of v4.10-rc2
> - fix typo in commit message of patch 1
> - add Mika's tag
>
> Andy Shevchenko (3):
> pwm: lpss: Avoid potential overflow of base_unit
> pwm: lpss: Allow duty cycle to be 0
> pwm: lpss: Switch to new atomic API
>
> Mika Westerberg (1):
> pwm: lpss: Do not export board infos for different PWM types
>
> drivers/pwm/pwm-lpss-pci.c | 20 +++----
> drivers/pwm/pwm-lpss-platform.c | 10 ++--
> drivers/pwm/pwm-lpss.c | 120 +++++++++++++++++++++-------------------
> drivers/pwm/pwm-lpss.h | 14 ++---
> 4 files changed, 81 insertions(+), 83 deletions(-)
>
> --
> 2.11.0
>
Tested-by: Ilkka Koskinen <ilkka.koskinen@intel.com>
Cheers, Ilkka
prev parent reply other threads:[~2017-01-05 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 9:16 [PATCH v2 0/4] pwm: lpss: clean up series Andy Shevchenko
2017-01-02 9:16 ` [PATCH v2 1/4] pwm: lpss: Avoid potential overflow of base_unit Andy Shevchenko
2017-01-02 9:16 ` [PATCH v2 2/4] pwm: lpss: Allow duty cycle to be 0 Andy Shevchenko
2017-01-02 9:16 ` [PATCH v2 3/4] pwm: lpss: Do not export board infos for different PWM types Andy Shevchenko
2017-01-18 11:11 ` Thierry Reding
2017-01-18 13:01 ` Mika Westerberg
2017-01-20 11:00 ` Thierry Reding
2017-01-20 11:15 ` Mika Westerberg
2017-01-20 11:18 ` Thierry Reding
2017-01-02 9:16 ` [PATCH v2 4/4] pwm: lpss: Switch to new atomic API Andy Shevchenko
2017-01-18 11:15 ` Thierry Reding
2017-01-19 14:32 ` Andy Shevchenko
2017-01-20 10:48 ` Thierry Reding
2017-01-05 8:09 ` Ilkka Koskinen [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=20170105080919.GA45669@kammari \
--to=ilkka.koskinen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-pwm@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=thierry.reding@gmail.com \
--cc=torvalds@linux-foundation.org \
/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).