From: Stefan Wahren <stefan.wahren@i2se.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Bryan Wu <cooloney@gmail.com>,
Thierry Reding <thierry.reding@gmail.com>,
linux-pwm@vger.kernel.org, linux-leds@vger.kernel.org,
Richard Purdie <rpurdie@rpsys.net>,
Sascha Hauer <s.hauer@pengutronix.de>,
kernel@pengutronix.de, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] leds/pwm: Don't disable pwm when setting brightness to 0
Date: Wed, 25 Feb 2015 09:13:26 +0100 [thread overview]
Message-ID: <54ED8426.6090401@i2se.com> (raw)
In-Reply-To: <20150224190636.GG7789@pengutronix.de>
Hi Uwe,
Am 24.02.2015 um 20:06 schrieb Uwe Kleine-König:
> Hello Stefan,
>
> On Tue, Feb 24, 2015 at 07:56:52PM +0100, Stefan Wahren wrote:
>> After replacing "i" with "priv->num_leds" in this patch we are able to use pwm
>> led with trigger heartbeat.
> Right, that's what I did in my tree to to please the build robot :-)
in that case, here is my:
Tested-by: Stefan Wahren <stefan.wahren@i2se.com>
>> This is the functional part of this issue, since the warning has been fixed [1]
> Can I interpret this as an Tested-by: for this patch and an Ack for
> patch 1?
Sorry, but i don't think i'm the right person for acking patch 1.
Stefan
> Best regards
> Uwe
>
next prev parent reply other threads:[~2015-02-25 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-12 9:44 [PATCH 0/2] leds/pwm: don't call pwm_disable when setting brightness Uwe Kleine-König
2015-02-12 9:44 ` [PATCH 1/2] pwm/doc: Clearify that the pin state after pwm_disable is undefined Uwe Kleine-König
2015-02-12 9:44 ` [PATCH 2/2] leds/pwm: Don't disable pwm when setting brightness to 0 Uwe Kleine-König
2015-02-12 9:47 ` Uwe Kleine-König
2015-02-24 18:56 ` Stefan Wahren
2015-02-24 19:06 ` Uwe Kleine-König
2015-02-25 8:13 ` Stefan Wahren [this message]
2015-02-25 8:42 ` Uwe Kleine-König
2015-03-25 10:14 ` [PATCH 0/2] leds/pwm: don't call pwm_disable when setting brightness Uwe Kleine-König
2015-03-25 12:00 ` Thierry Reding
2015-03-27 8:59 ` Uwe Kleine-König
2015-03-27 11:26 ` Thierry Reding
2015-03-27 14:35 ` Uwe Kleine-König
2015-03-27 15:43 ` Thierry Reding
2015-03-27 18:49 ` Sascha Hauer
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=54ED8426.6090401@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=cooloney@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=s.hauer@pengutronix.de \
--cc=thierry.reding@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).