From: Pavel Machek <pavel@ucw.cz>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, linux-leds@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/3] as3645a: Use ams,input-max-microamp as documented in DT bindings
Date: Fri, 8 Sep 2017 15:14:46 +0200 [thread overview]
Message-ID: <20170908131446.GP18365@amd> (raw)
In-Reply-To: <20170908124213.18904-2-sakari.ailus@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 552 bytes --]
On Fri 2017-09-08 15:42:11, Sakari Ailus wrote:
> DT bindings document the property "ams,input-max-microamp" that limits the
> chip's maximum input current. The driver and the DTS however used
> "peak-current-limit" property. Fix this by using the property documented
> in DT binding documentation.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-09-08 13:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 12:42 [PATCH 0/3] AS3645A fixes Sakari Ailus
2017-09-08 12:42 ` [PATCH 2/3] dt: bindings: as3645a: Use LED number to refer to LEDs Sakari Ailus
2017-09-13 20:28 ` Rob Herring
[not found] ` <20170908124213.18904-1-sakari.ailus-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2017-09-08 12:42 ` [PATCH 1/3] as3645a: Use ams,input-max-microamp as documented in DT bindings Sakari Ailus
2017-09-08 12:42 ` Sakari Ailus
2017-09-08 13:14 ` Pavel Machek [this message]
2017-09-08 12:42 ` [PATCH 3/3] as3645a: Use integer numbers for parsing LEDs Sakari Ailus
2017-09-08 12:42 ` Sakari Ailus
2017-09-08 13:17 ` Pavel Machek
2017-09-08 13:23 ` Sakari Ailus
2017-09-08 13:38 ` Pavel Machek
2017-09-08 13:45 ` Sakari Ailus
2017-09-08 13:45 ` Sakari Ailus
2017-09-08 19:51 ` [PATCH 0/3] AS3645A fixes Jacek Anaszewski
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=20170908131446.GP18365@amd \
--to=pavel@ucw.cz \
--cc=devicetree@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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.