devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: sakari.ailus@iki.fi, devicetree@vger.kernel.org,
	linux-leds@vger.kernel.org, linux-doc@vger.kernel.org,
	cooloney@gmail.com, rpurdie@rpsys.net, robh+dt@kernel.org,
	pawel.moll@arm.com, mark.rutland@arm.com,
	ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
	rob@landley.net
Subject: Re: [PATCH] Add attributes neccessary for LED flashes to devicetree/bindings/leds/common.txt
Date: Thu, 20 Nov 2014 21:52:55 +0100	[thread overview]
Message-ID: <20141120205254.GA19174@amd> (raw)
In-Reply-To: <546DFF3A.7020702@samsung.com>

On Thu 2014-11-20 15:48:26, Jacek Anaszewski wrote:
> On 11/20/2014 02:38 PM, Jacek Anaszewski wrote:
> >Hi Pavel,
> >
> >On 11/20/2014 02:17 PM, Pavel Machek wrote:
> >>
> >>Add attributes neccessary for LED flashes to
> >>devicetree/bindings/leds/common.txt .
> >>
> >>This will allow me to add device tree support for adp1653 i2c flash
> >>LED driver, and allow Jacek Anaszewski to add support for more LED
> >>drivers..
..
> 
> Actually, we've agreed with Sakari that we can handle
> indicator-pattern later.

Good.

> I would remove references to you, me and adp1653 driver from the commit
> message and mention that this modifications adjust the led common
> bindings to the LED Flash class that is to be added.

Ok, who can take this patch? Can you edit the changelog, or should I
do it? Anything else that needs changing?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2014-11-20 20:52 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20 13:17 [PATCH] Add attributes neccessary for LED flashes to devicetree/bindings/leds/common.txt Pavel Machek
2014-11-20 13:38 ` Jacek Anaszewski
2014-11-20 14:48   ` Jacek Anaszewski
2014-11-20 20:52     ` Pavel Machek [this message]
2014-11-21  8:15       ` Jacek Anaszewski
2014-11-24 22:53         ` Pavel Machek
2014-11-26  6:09           ` Bryan Wu
2014-12-03 15:51             ` Pavel Machek
2014-12-03 16:10               ` Sakari Ailus
2014-12-03 18:58             ` Pavel Machek
2014-11-20 19:19   ` Pavel Machek
2014-11-20 15:03 ` Sakari Ailus
2014-11-20 20:53   ` Pavel Machek
2014-11-21  7:39     ` Sakari Ailus
2014-11-26 12:47       ` Pavel Machek
2014-11-21  7:38   ` Jacek Anaszewski
2014-11-21  7:40     ` Sakari Ailus
2014-12-03 16:03     ` Sakari Ailus
2014-11-26  7:57 ` Jacek Anaszewski
2014-12-03 18:57 ` [PATCH w/ acks] DT: leds: Add flash LED devices related properties Pavel Machek
2014-12-03 19:03   ` Bryan Wu
2014-12-20 15:02     ` Pavel Machek
2014-12-22  2:27   ` Rob Herring
2014-12-22 11:45     ` Pavel Machek

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=20141120205254.GA19174@amd \
    --to=pavel@ucw.cz \
    --cc=cooloney@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=galak@codeaurora.org \
    --cc=ijc+devicetree@hellion.org.uk \
    --cc=j.anaszewski@samsung.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pawel.moll@arm.com \
    --cc=rob@landley.net \
    --cc=robh+dt@kernel.org \
    --cc=rpurdie@rpsys.net \
    --cc=sakari.ailus@iki.fi \
    /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).