From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/4] DT support for LaCie 2Big and 5Big Network v2
Date: Fri, 23 May 2014 20:23:06 +0200 [thread overview]
Message-ID: <20140523182306.GD31314@lunn.ch> (raw)
In-Reply-To: <20140523180242.GM6755@kw.sim.vm.gnt>
On Fri, May 23, 2014 at 08:02:42PM +0200, Simon Guinot wrote:
> On Sun, May 11, 2014 at 10:21:48PM +0200, Andrew Lunn wrote:
> > v3:
> > gpio_poweroff -> gpio-poweroff, etc.
> > Add stdout-path
> > Remove pinctrl property from spi, set in kirkwood.dtsi.
> >
> > Andrew Lunn (4):
> > ARM: Kirkwood: Add board file for netxbig LEDs
> > ARM: Kirkwood: Add DT descriptions for net2big and net5big.
> > ARM: mvebu: Add LaCie 2Big and 5Big Network v2
> > ARM: multi_v5: Enable LaCie 2Big and 5Big Network v2
> >
> > arch/arm/boot/dts/Makefile | 2 +
> > arch/arm/boot/dts/kirkwood-net2big.dts | 30 +++++
> > arch/arm/boot/dts/kirkwood-net5big.dts | 83 ++++++++++++++
> > arch/arm/boot/dts/kirkwood-netxbig.dtsi | 166 +++++++++++++++++++++++++++
> > arch/arm/configs/multi_v5_defconfig | 1 +
> > arch/arm/configs/mvebu_v5_defconfig | 1 +
> > arch/arm/mach-mvebu/Kconfig | 7 ++
> > arch/arm/mach-mvebu/Makefile | 1 +
> > arch/arm/mach-mvebu/board-netxbig.c | 191 ++++++++++++++++++++++++++++++++
> > arch/arm/mach-mvebu/board.h | 5 +
> > arch/arm/mach-mvebu/kirkwood.c | 3 +
> > 11 files changed, 490 insertions(+)
> > create mode 100644 arch/arm/boot/dts/kirkwood-net2big.dts
> > create mode 100644 arch/arm/boot/dts/kirkwood-net5big.dts
> > create mode 100644 arch/arm/boot/dts/kirkwood-netxbig.dtsi
> > create mode 100644 arch/arm/mach-mvebu/board-netxbig.c
>
> Hi Andrew,
>
> I have successfully tested your patch series (on the top of Linux
> 3.15-rc6) on a 2Big Network v2 board.
Great, thanks.
> Unfortunately, I failed to test the 5Big Network v2 support. My power
> supply died :( And since the connector is very specific, I have to wait
> until next Tuesday to get an another one.
O.K. I think we have missed the merge window for this cycle anyway, so
take your time.
> Moreover, I have a question. The DT support for the d2 Network v2
> board (d2net_v2) is still missing. Since this board is very close
> from the 2Big Network v2, I think it should be included in this
> patch series. Do you want me to take care of that ?
Humm, i thought Thomas had done that conversion. However, it looks
like his patches never got picked up:
http://www.spinics.net/lists/arm-kernel/msg263520.html
It would be great if you can finish them off.
Andrew
prev parent reply other threads:[~2014-05-23 18:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 20:21 [PATCH v3 0/4] DT support for LaCie 2Big and 5Big Network v2 Andrew Lunn
2014-05-11 20:21 ` [PATCH v3 1/4] ARM: Kirkwood: Add board file for netxbig LEDs Andrew Lunn
2014-05-11 20:21 ` [PATCH v3 2/4] ARM: Kirkwood: Add DT descriptions for net2big and net5big Andrew Lunn
2014-05-23 18:32 ` Simon Guinot
2014-05-11 20:21 ` [PATCH v3 3/4] ARM: mvebu: Add LaCie 2Big and 5Big Network v2 Andrew Lunn
2014-05-23 18:33 ` Simon Guinot
2014-05-11 20:21 ` [PATCH v3 4/4] ARM: multi_v5: Enable " Andrew Lunn
2014-05-23 18:34 ` Simon Guinot
2014-05-23 18:02 ` [PATCH v3 0/4] DT support for " Simon Guinot
2014-05-23 18:06 ` Jason Cooper
2014-05-23 18:23 ` Andrew Lunn [this message]
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=20140523182306.GD31314@lunn.ch \
--to=andrew@lunn.ch \
--cc=linux-arm-kernel@lists.infradead.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.