All of lore.kernel.org
 help / color / mirror / Atom feed
From: andrew@lunn.ch (Andrew Lunn)
To: linux-arm-kernel@lists.infradead.org
Subject: kirkwood, nand, clocks and device-tree
Date: Sun, 20 May 2012 15:22:14 +0200	[thread overview]
Message-ID: <20120520132214.GD12741@lunn.ch> (raw)
In-Reply-To: <alpine.DEB.2.00.1205201352090.23719@marmot.wormnet.eu>

> I should really submit this :) What should it be based on? A new
> revision of my previous patches, or should I assume that my work and
> Andrew's clk work have already been merged? (apologies if this is a
> dumb question)

Yes, you can assume both are in. arm-soc has them, so the 3.5-rc1
should have them.

For the next cycle we need to improve working together on DT porting.
There is a lot of work going on here, in kirkwood, orion5x, dove, and
the two new Armada SoCs, all needing/porting drivers to DT.  I think
we need a tree where patches are quickly added once they are stable,
so that others can profit from the work.

       Andrew

  reply	other threads:[~2012-05-20 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18  9:50 kirkwood, nand, clocks and device-tree Arnaud Patard (Rtp)
2012-05-20  9:51 ` Andrew Lunn
2012-05-20 13:05   ` Jamie Lentin
2012-05-20 13:22     ` Andrew Lunn [this message]
2012-05-21  1:08       ` Jason Cooper
2012-05-21  5:23         ` Andrew Lunn
2012-05-21 15:57           ` Jason Cooper
2012-05-21 17:35             ` Andrew Lunn
2012-05-21 18:11               ` Jason Cooper
2012-05-22  7:33                 ` Arnd Bergmann
2012-05-22 12:42                   ` Jason Cooper
2012-05-21  1:12     ` Jason Cooper
2012-05-21 21:55       ` [PATCH] ARM: kirkwood: Force nand platform device name Jamie Lentin

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=20120520132214.GD12741@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.