From: Tony Lindgren <tony@atomide.com>
To: Sebastian Reichel <sre@debian.org>
Cc: "Sebastian Reichel" <sre@ring0.de>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Bryan Wu" <cooloney@gmail.com>,
"Richard Purdie" <rpurdie@rpsys.net>,
"Rob Herring" <rob.herring@calxeda.com>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Stephen Warren" <swarren@wwwdotorg.org>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Russell King" <linux@arm.linux.org.uk>,
"Rob Landley" <rob@landley.net>,
"Linus Walleij" <linus.walleij@linaro.org>,
"Milo Kim" <milo.kim@ti.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, linux-omap@vger.kernel.org
Subject: Re: [PATCH 1/2] leds: lp55xx: handle enable pin in driver
Date: Tue, 22 Oct 2013 10:06:04 -0700 [thread overview]
Message-ID: <20131022170604.GP15154@atomide.com> (raw)
In-Reply-To: <1382446896-28436-2-git-send-email-sre@debian.org>
* Sebastian Reichel <sre@debian.org> [131022 06:02]:
> This patch moves the handling of the chip's enable pin from the board
> code into the driver. It also updates all board-code files using the
> driver to incorporate this change.
>
> This is needed for device tree support of the enable pin.
This seems safe to merge along with the other LED patches, the
changes to arch/arm/mach-omap2 should not conflict with anything.
So for the arch/arm/mach-omap2 changes:
Acked-by: Tony Lindgren <tony@atomide.com>
WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] leds: lp55xx: handle enable pin in driver
Date: Tue, 22 Oct 2013 10:06:04 -0700 [thread overview]
Message-ID: <20131022170604.GP15154@atomide.com> (raw)
In-Reply-To: <1382446896-28436-2-git-send-email-sre@debian.org>
* Sebastian Reichel <sre@debian.org> [131022 06:02]:
> This patch moves the handling of the chip's enable pin from the board
> code into the driver. It also updates all board-code files using the
> driver to incorporate this change.
>
> This is needed for device tree support of the enable pin.
This seems safe to merge along with the other LED patches, the
changes to arch/arm/mach-omap2 should not conflict with anything.
So for the arch/arm/mach-omap2 changes:
Acked-by: Tony Lindgren <tony@atomide.com>
next prev parent reply other threads:[~2013-10-22 17:06 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 13:01 [PATCH 0/2] Add lp5523 DT support Sebastian Reichel
2013-10-22 13:01 ` Sebastian Reichel
2013-10-22 13:01 ` [PATCH 1/2] leds: lp55xx: handle enable pin in driver Sebastian Reichel
2013-10-22 13:01 ` Sebastian Reichel
2013-10-22 16:57 ` Linus Walleij
2013-10-22 16:57 ` Linus Walleij
2013-10-22 16:58 ` Linus Walleij
2013-10-22 16:58 ` Linus Walleij
2013-10-22 17:06 ` Tony Lindgren [this message]
2013-10-22 17:06 ` Tony Lindgren
2013-10-22 17:22 ` Bryan Wu
2013-10-22 17:22 ` Bryan Wu
2013-10-22 17:37 ` Tony Lindgren
2013-10-22 17:37 ` Tony Lindgren
2013-10-22 17:46 ` Bryan Wu
2013-10-22 17:46 ` Bryan Wu
[not found] ` <CAK5ve-JhehHHAU_2tN-RVb8+u2AbUS_Yx=k+i0Ponnm9Wir+OQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-10-23 8:19 ` Tony Lindgren
2013-10-23 8:19 ` Tony Lindgren
2013-10-23 8:19 ` Tony Lindgren
2013-10-23 8:41 ` Benoit Cousson
2013-10-23 8:41 ` Benoit Cousson
2013-10-22 13:01 ` [PATCH 2/2] DTS: ARM: OMAP3-N900: Add LP5523 support Sebastian Reichel
2013-10-22 13:01 ` Sebastian Reichel
2013-10-22 17:38 ` Tony Lindgren
2013-10-22 17:38 ` Tony Lindgren
2013-10-22 17:47 ` Bryan Wu
2013-10-22 17:47 ` Bryan Wu
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=20131022170604.GP15154@atomide.com \
--to=tony@atomide.com \
--cc=bcousson@baylibre.com \
--cc=cooloney@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mark.rutland@arm.com \
--cc=milo.kim@ti.com \
--cc=pawel.moll@arm.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=rpurdie@rpsys.net \
--cc=sre@debian.org \
--cc=sre@ring0.de \
--cc=swarren@wwwdotorg.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 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.