linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: kaloz@openwrt.org (Imre Kaloz)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: orion5x: convert Netgear WNR854T to device tree
Date: Tue, 20 Nov 2012 08:21:22 +0100	[thread overview]
Message-ID: <op.wn19dwpw2s3iss@ecaz> (raw)
In-Reply-To: <20121119204641.GK22106@titan.lakedaemon.net>

Jason,

On Mon, 19 Nov 2012 21:46:41 +0100, Jason Cooper <jason@lakedaemon.net> wrote:

> On Mon, Nov 19, 2012 at 05:27:31PM +0100, Imre Kaloz wrote:
>> This commit converts the Netgear WNR854T to device tree
>>
>> Signed-off-by: Imre Kaloz <kaloz@openwrt.org>
>> ---
>>  arch/arm/boot/dts/Makefile                    |    3 +-
>>  arch/arm/boot/dts/orion5x-netgear-wnr854t.dts |   83 +++++++++++++++++++++++++
>>  arch/arm/mach-orion5x/Kconfig                 |    7 +-
>>  arch/arm/mach-orion5x/Makefile                |    2 +-
>>  arch/arm/mach-orion5x/board-dt.c              |    3 +
>>  arch/arm/mach-orion5x/common.h                |    5 ++
>>  arch/arm/mach-orion5x/wnr854t-setup.c         |   59 +-----------------
>>  7 files changed, 99 insertions(+), 63 deletions(-)
>>  create mode 100644 arch/arm/boot/dts/orion5x-netgear-wnr854t.dts
>
> One last thing, could you use savedefconfig and update orion5x_defconfig
> to include your new board?  It can be a part of the same patch.

Would you prefer it to be included in this one or in a later patch if I'm done adding some more boards?


Thanks,

Imre

  reply	other threads:[~2012-11-20  7:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-19 16:27 [PATCH] arm: orion5x: convert Netgear WNR854T to device tree Imre Kaloz
2012-11-19 16:44 ` Thomas Petazzoni
2012-11-19 18:24 ` Jason Cooper
2012-11-19 20:46 ` Jason Cooper
2012-11-20  7:21   ` Imre Kaloz [this message]
2012-11-20 12:28     ` Jason Cooper
2012-11-21 21:06       ` Jason Cooper

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=op.wn19dwpw2s3iss@ecaz \
    --to=kaloz@openwrt.org \
    --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 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).