From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: Kirkwood: new boards for v3.5
Date: Tue, 15 May 2012 09:47:27 +0100 [thread overview]
Message-ID: <4FB2181F.7010609@codethink.co.uk> (raw)
In-Reply-To: <20120515032605.GV16338@titan.lakedaemon.net>
On 15/05/12 04:26, Jason Cooper wrote:
> The following changes since commit 36be50515fe2aef61533b516fa2576a2c7fe7664:
>
> Linux 3.4-rc7 (2012-05-12 18:37:47 -0700)
>
> are available in the git repository at:
> git://git.infradead.org/users/jcooper/linux.git kirkwood_boards_for_v3.5
>
> Arnaud Patard (3):
> kirkwood/orion: fix orion_gpio_set_blink
> orion/kirkwood: create a generic function for gpio led blinking
> kirkwood: Add iconnect support
>
> Jamie Lentin (4):
> ARM: kirkwood: Basic support for DNS-320 and DNS-325
> mtd: Add orion_nand devicetree bindings
> kirkwood: Allow nand to be configured via. devicetree
> ARM: kirkwood: Define DNS-320/DNS-325 NAND in fdt
>
> Simon Baatz (1):
> ARM: kirkwood: Add support for RaidSonic IB-NAS6210/6220 using devicetree
>
> .../devicetree/bindings/mtd/orion-nand.txt | 50 ++++
> arch/arm/boot/dts/kirkwood-dns320.dts | 64 +++++
> arch/arm/boot/dts/kirkwood-dns325.dts | 59 +++++
> arch/arm/boot/dts/kirkwood-ib62x0.dts | 44 +++
> arch/arm/boot/dts/kirkwood-iconnect.dts | 26 ++
I thought the idea of going to device-tree was to remove the addition
of these? Now instead of .c files we're getting piles of .dts files.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
next prev parent reply other threads:[~2012-05-15 8:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-15 3:26 [GIT PULL] ARM: Kirkwood: new boards for v3.5 Jason Cooper
2012-05-15 8:44 ` Arnd Bergmann
2012-05-15 8:47 ` Ben Dooks [this message]
2012-05-15 19:25 ` Nicolas Pitre
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=4FB2181F.7010609@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--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.