devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Denis Osterland-Heim <denis.osterland@diehl.com>
Cc: "dmurphy@ti.com" <dmurphy@ti.com>,
	"jacek.anaszewski@gmail.com" <jacek.anaszewski@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v5 1/3] leds: pwm: check result of led_pwm_set() in led_pwm_add()
Date: Mon, 27 Apr 2020 11:36:50 +0200	[thread overview]
Message-ID: <20200427093650.GA20954@duo.ucw.cz> (raw)
In-Reply-To: <20200421130644.16059-2-Denis.Osterland@diehl.com>

[-- Attachment #1: Type: text/plain, Size: 451 bytes --]

On Tue 2020-04-21 13:09:14, Denis Osterland-Heim wrote:
> led_pwm_set() now returns an error when setting the PWM fails.
> 
> Signed-off-by: Denis Osterland-Heim <Denis.Osterland@diehl.com>

Thanks, applied. (Just this patch for now).
                                                                Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2020-04-27  9:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-21 13:09 [PATCH v5 0/3] leds: pwm: add support for default-state device Denis Osterland-Heim
2020-04-21 13:09 ` [PATCH v5 1/3] leds: pwm: check result of led_pwm_set() in led_pwm_add() Denis Osterland-Heim
2020-04-27  9:36   ` Pavel Machek [this message]
2020-04-21 13:09 ` [PATCH v5 2/3] leds: pwm: add support for default-state device property Denis Osterland-Heim
2020-04-21 13:09 ` [PATCH v5 3/3] leds: pwm: add reference to common leds for default-state Denis Osterland-Heim

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=20200427093650.GA20954@duo.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=denis.osterland@diehl.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmurphy@ti.com \
    --cc=jacek.anaszewski@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=robh+dt@kernel.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).