All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Stefan Wahren <stefan.wahren@i2se.com>
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: Tue, 24 Feb 2015 20:06:36 +0100	[thread overview]
Message-ID: <20150224190636.GG7789@pengutronix.de> (raw)
In-Reply-To: <1151818200.134325.1424804213026.JavaMail.open-xchange@oxbsltgw03.schlund.de>

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 :-)

> 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?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

WARNING: multiple messages have this Message-ID (diff)
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] leds/pwm: Don't disable pwm when setting brightness to 0
Date: Tue, 24 Feb 2015 20:06:36 +0100	[thread overview]
Message-ID: <20150224190636.GG7789@pengutronix.de> (raw)
In-Reply-To: <1151818200.134325.1424804213026.JavaMail.open-xchange@oxbsltgw03.schlund.de>

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 :-)

> 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?

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2015-02-24 19:06 UTC|newest]

Thread overview: 30+ 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 ` 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   ` 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:44   ` Uwe Kleine-König
2015-02-12  9:47   ` Uwe Kleine-König
2015-02-12  9:47     ` Uwe Kleine-König
2015-02-24 18:56   ` Stefan Wahren
2015-02-24 18:56     ` Stefan Wahren
2015-02-24 19:06     ` Uwe Kleine-König [this message]
2015-02-24 19:06       ` Uwe Kleine-König
2015-02-25  8:13       ` Stefan Wahren
2015-02-25  8:13         ` Stefan Wahren
2015-02-25  8:42         ` Uwe Kleine-König
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 10:14   ` Uwe Kleine-König
2015-03-25 12:00   ` Thierry Reding
2015-03-25 12:00     ` Thierry Reding
2015-03-27  8:59     ` Uwe Kleine-König
2015-03-27  8:59       ` Uwe Kleine-König
2015-03-27 11:26       ` Thierry Reding
2015-03-27 11:26         ` Thierry Reding
2015-03-27 14:35         ` Uwe Kleine-König
2015-03-27 14:35           ` Uwe Kleine-König
2015-03-27 15:43           ` Thierry Reding
2015-03-27 15:43             ` Thierry Reding
2015-03-27 18:49             ` Sascha Hauer
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=20150224190636.GG7789@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --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=stefan.wahren@i2se.com \
    --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 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.