From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>, linux-leds@vger.kernel.org
Cc: Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Pavel Machek <pavel@ucw.cz>,
Sylwester Nawrocki <s.nawrocki@samsung.com>,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6] DT: leds: Improve description of flash LEDs related properties
Date: Fri, 10 Apr 2015 12:14:53 +0300 [thread overview]
Message-ID: <5527948D.1020603@linux.intel.com> (raw)
In-Reply-To: <1428655016-17752-1-git-send-email-j.anaszewski@samsung.com>
Hi Jacek,
Thank you for the quick update!
Jacek Anaszewski wrote:
> 1. Since max-microamp property has had no users so far, then rename
> it to more descriptive led-max-microamp.
> 2. Since flash-timeout-us property has had no users so far, then rename
> it to more accurate flash-max-timeout-us.
> 3. Describe led-max-microamp property as mandatory for specific board
> configurations.
> 4. Make flash-max-microamp and flash-max-timeout-us properties mandatory
> for devices with configurable flash current and flash timeout settings
> respectively.
>
> Signed-off-by: Jacek Anaszewski <j.anaszewski@samsung.com>
> Cc: Bryan Wu <cooloney@gmail.com>
> Cc: Richard Purdie <rpurdie@rpsys.net>
> Cc: Pavel Machek <pavel@ucw.cz>
> Cc: Sakari Ailus <sakari.ailus@linux.intel.com>
> Cc: Sylwester Nawrocki <s.nawrocki@samsung.com>
> Cc: devicetree@vger.kernel.org
Acked-by: Sakari Ailus <sakari.ailus@linux.intel.com>
--
Kind regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2015-04-10 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 8:36 [PATCH v6] DT: leds: Improve description of flash LEDs related properties Jacek Anaszewski
2015-04-10 9:14 ` Sakari Ailus [this message]
[not found] ` <1428655016-17752-1-git-send-email-j.anaszewski-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-04-10 10:07 ` Sylwester Nawrocki
2015-04-13 8:43 ` 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=5527948D.1020603@linux.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=j.anaszewski@samsung.com \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.net \
--cc=s.nawrocki@samsung.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 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).