From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/3] Add DT support for netxbig LEDs
Date: Mon, 16 Mar 2015 17:01:10 +0100 [thread overview]
Message-ID: <5506FE46.4000405@free-electrons.com> (raw)
In-Reply-To: <20150309094107.GL1509@kw.sim.vm.gnt>
Hi all,
On 09/03/2015 10:41, Simon Guinot wrote:
> On Mon, Feb 23, 2015 at 04:04:18PM +0100, Simon Guinot wrote:
>> Hello,
>>
>> This patch series adds DT support for the LEDs found on the Kirkwood-based
>> LaCie boards 2Big and 5Big Network v2.
>>
>> Simon
>>
>> Simon Guinot (3):
>> leds: netxbig: add device tree binding
>> ARM: Kirkwood: add LED DT entries for netxbig boards
>> ARM: mvebu: remove static LED setup for netxbig boards
>
> Hi Brian,
>
> Please, consider merging the first patch of this serie.
Brian,
here again let me know when this patch will be merged, and I will
also need a stable tag as patch 2 depends on this one.
Andrew, Jason,
patch 2 and 3 looks OK for me. What is your opinion about it?
Thanks,
Gregory
>
> Thanks in advance.
>
> Simon
>
>>
>> .../devicetree/bindings/gpio/netxbig-gpio-ext.txt | 22 ++
>> .../devicetree/bindings/leds/leds-netxbig.txt | 90 ++++++++
>> arch/arm/boot/dts/kirkwood-net5big.dts | 60 +++++
>> arch/arm/boot/dts/kirkwood-netxbig.dtsi | 80 +++++++
>> arch/arm/mach-mvebu/Kconfig | 7 -
>> arch/arm/mach-mvebu/Makefile | 1 -
>> arch/arm/mach-mvebu/board.h | 21 --
>> arch/arm/mach-mvebu/kirkwood.c | 4 -
>> arch/arm/mach-mvebu/netxbig.c | 191 ----------------
>> drivers/leds/leds-netxbig.c | 244 +++++++++++++++++++--
>> include/dt-bindings/leds/leds-netxbig.h | 18 ++
>> 11 files changed, 493 insertions(+), 245 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/gpio/netxbig-gpio-ext.txt
>> create mode 100644 Documentation/devicetree/bindings/leds/leds-netxbig.txt
>> delete mode 100644 arch/arm/mach-mvebu/board.h
>> delete mode 100644 arch/arm/mach-mvebu/netxbig.c
>> create mode 100644 include/dt-bindings/leds/leds-netxbig.h
>>
>> --
>> 2.1.1
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel at lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2015-03-16 16:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 15:04 [PATCH 0/3] Add DT support for netxbig LEDs Simon Guinot
2015-02-23 15:04 ` [PATCH 1/3] leds: netxbig: add device tree binding Simon Guinot
2015-02-23 15:04 ` [PATCH 2/3] ARM: Kirkwood: add LED DT entries for netxbig boards Simon Guinot
2015-02-23 15:04 ` [PATCH 3/3] ARM: mvebu: remove static LED setup " Simon Guinot
2015-03-09 9:41 ` [PATCH 0/3] Add DT support for netxbig LEDs Simon Guinot
2015-03-16 16:01 ` Gregory CLEMENT [this message]
2015-03-30 8:30 ` Simon Guinot
2015-03-30 12:30 ` Andrew Lunn
2015-03-30 13:22 ` Jason Cooper
2015-03-30 13:29 ` Gregory CLEMENT
2015-03-30 13:46 ` Jason Cooper
2015-03-30 14:20 ` Gregory CLEMENT
2015-03-23 10:31 ` Simon Guinot
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=5506FE46.4000405@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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