From: ian.molton@codethink.co.uk (Ian Molton)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 3/6] mv643xx.c: Add basic device tree support.
Date: Wed, 01 Aug 2012 09:50:57 +0100 [thread overview]
Message-ID: <5018EDF1.40709@codethink.co.uk> (raw)
In-Reply-To: <20120731164652.GD28852@lunn.ch>
On 31/07/12 17:46, Andrew Lunn wrote:
> Hi Ian
>
> Probably the driver change will get upstream by netdev. The rest will
> go via the Orion maintainers into arm-soc. So you should probably move
> this board-dt.c change into a patch of its own, or make it part of:
>
> csb1724: Enable device tree based mv643xx ethernet support.
Its not csb1724 specific; I've merged it into
kirkwood: Add a clock setup helper for mv643xx ethernet.
and renamed it to:
kirkwood: Add fixups for DT based mv643xx ethernet.
As this described its purpose better. Hopefully in time, we can
pass something in DT that will allow us to remove that code.
-Ian
WARNING: multiple messages have this Message-ID (diff)
From: Ian Molton <ian.molton@codethink.co.uk>
To: linux-arm-kernel@lists.infradead.org, andrew@lunn.ch,
thomas.petazzoni@free-electrons.com, ben.dooks@codethink.co.uk,
arnd@arndb.de, netdev@vger.kernel.org
Subject: Re: [PATCH v2 3/6] mv643xx.c: Add basic device tree support.
Date: Wed, 01 Aug 2012 09:50:57 +0100 [thread overview]
Message-ID: <5018EDF1.40709@codethink.co.uk> (raw)
In-Reply-To: <20120731164652.GD28852@lunn.ch>
On 31/07/12 17:46, Andrew Lunn wrote:
> Hi Ian
>
> Probably the driver change will get upstream by netdev. The rest will
> go via the Orion maintainers into arm-soc. So you should probably move
> this board-dt.c change into a patch of its own, or make it part of:
>
> csb1724: Enable device tree based mv643xx ethernet support.
Its not csb1724 specific; I've merged it into
kirkwood: Add a clock setup helper for mv643xx ethernet.
and renamed it to:
kirkwood: Add fixups for DT based mv643xx ethernet.
As this described its purpose better. Hopefully in time, we can
pass something in DT that will allow us to remove that code.
-Ian
next prev parent reply other threads:[~2012-08-01 8:50 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-31 15:45 [PATCH v2 0/6] mv643xx Ethernet DT support and CSB1724 board support Ian Molton
2012-07-31 15:45 ` Ian Molton
2012-07-31 15:45 ` [PATCH v2 1/6] Initial csb1724 board support (FDT) Ian Molton
2012-07-31 15:45 ` Ian Molton
2012-07-31 16:43 ` Andrew Lunn
2012-07-31 16:43 ` Andrew Lunn
2012-07-31 15:45 ` [PATCH v2 2/6] mv643xx.c: Remove magic numbers Ian Molton
2012-07-31 15:45 ` Ian Molton
2012-07-31 15:45 ` [PATCH v2 3/6] mv643xx.c: Add basic device tree support Ian Molton
2012-07-31 15:45 ` Ian Molton
2012-07-31 16:46 ` Andrew Lunn
2012-07-31 16:46 ` Andrew Lunn
2012-08-01 8:50 ` Ian Molton [this message]
2012-08-01 8:50 ` Ian Molton
2012-07-31 18:23 ` Arnd Bergmann
2012-07-31 18:23 ` Arnd Bergmann
2012-07-31 19:24 ` Andrew Lunn
2012-07-31 19:24 ` Andrew Lunn
2012-07-31 20:18 ` Arnd Bergmann
2012-07-31 20:18 ` Arnd Bergmann
2012-07-31 15:45 ` [PATCH v2 4/6] kirkwood: Add a clock setup helper for mv643xx ethernet Ian Molton
2012-07-31 15:45 ` [PATCH v2 5/6] csb1724: Enable device tree based mv643xx ethernet support Ian Molton
2012-07-31 15:45 ` Ian Molton
2012-07-31 15:45 ` [PATCH v2 6/6] DT: Convert all kirkwood boards with mv643xx that use DT Ian Molton
2012-07-31 15:45 ` Ian Molton
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=5018EDF1.40709@codethink.co.uk \
--to=ian.molton@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.