From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Status of arch/arm in linux-next
Date: Mon, 18 Apr 2011 11:10:52 +0300 [thread overview]
Message-ID: <20110418081050.GG12272@atomide.com> (raw)
In-Reply-To: <20110416165725.GA25811@opensource.wolfsonmicro.com>
* Mark Brown <broonie@opensource.wolfsonmicro.com> [110416 19:54]:
> On Sat, Apr 16, 2011 at 09:28:02AM +0100, Russell King - ARM Linux wrote:
>
> > Towards the end of the cycle, we may be able to consider some platforms,
> > but _only_ if they make use of the consolidated features and therefore
> > have _minimal_ additional code.
>
> ...this is the negative side of the message - what we're not willing to
> accept. What's the positive side of the message, what can people do to
> help? What is the level of consolidation work that's needed before we
> can develop again, and what's needed to make progress there?
I gues a large chunk of the consolidation work will happen only after
we have some new frameworks in place.
But meanwhile there is still tons of work left to do in coalescing
code just within the various ARM architectures.
I think we _should_ accept new platforms if they're sane as we
don't have any alternative available.
But with the existing platforms, I think that the policy for the
next merge window should be that more code disappears than gets
added.
> For example, with support for new machines are we saying that for
> example we're going to refuse to accept anything that isn't device tree
> based? If so then what needs doing?
Well we can't require that until the device tree code is merged.
And for older platforms, we need the device tree append support.
It seems that there is still at least one problem with the device
tree append support, but once that's sorted out we should
probably merge that code.
Adding a new machine should be a minimal amount of code already.
So with existing platforms that amount of code can be "exchanged"
for some platform code consolidation patches :)
Regards,
Tony
next prev parent reply other threads:[~2011-04-18 8:10 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-14 9:44 Status of arch/arm in linux-next Russell King - ARM Linux
2011-04-14 11:08 ` Tony Lindgren
2011-04-14 12:02 ` Russell King - ARM Linux
2011-04-14 12:31 ` Tony Lindgren
2011-04-14 14:20 ` Mark Brown
2011-04-14 14:26 ` Tony Lindgren
2011-04-14 14:31 ` Russell King - ARM Linux
2011-04-14 18:32 ` Mark Brown
2011-04-15 15:12 ` Grant Likely
2011-04-15 15:56 ` Russell King - ARM Linux
2011-04-15 16:10 ` Grant Likely
2011-04-16 8:28 ` Russell King - ARM Linux
2011-04-16 16:57 ` Mark Brown
2011-04-18 8:10 ` Tony Lindgren [this message]
2011-04-18 13:57 ` Mark Brown
2011-04-18 14:41 ` Tony Lindgren
2011-04-18 14:41 ` Tony Lindgren
2011-04-18 15:58 ` Mark Brown
2011-04-18 15:58 ` Mark Brown
2011-04-18 17:18 ` Russell King - ARM Linux
2011-04-18 20:23 ` Mark Brown
2011-04-18 21:40 ` Thomas Gleixner
2011-04-18 23:55 ` Mark Brown
2011-04-14 14:07 ` Mark Brown
2011-04-15 2:59 ` Nico Erfurth
2011-04-15 8:21 ` Nicolas Ferre
2011-04-15 13:13 ` Nico Erfurth
2011-04-15 1:16 ` Linus Walleij
2011-04-15 6:26 ` Tony Lindgren
2011-04-19 14:16 ` Arnd Bergmann
2011-04-19 14:50 ` Mark Brown
2011-04-19 14:55 ` Arnd Bergmann
2011-04-19 15:04 ` Mark Brown
2011-04-19 15:14 ` Linus Walleij
2011-04-19 16:01 ` Arnd Bergmann
2011-04-19 16:01 ` Arnd Bergmann
2011-04-19 16:05 ` Mark Brown
2011-04-19 16:05 ` Mark Brown
2011-04-21 20:14 ` Dave Jones
2011-04-21 20:14 ` Dave Jones
2011-04-21 21:02 ` Nicolas Pitre
2011-04-21 21:02 ` Nicolas Pitre
2011-04-22 7:17 ` Tony Lindgren
2011-04-22 7:17 ` Tony Lindgren
2011-04-26 14:05 ` Arnd Bergmann
2011-04-26 14:05 ` Arnd Bergmann
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 17:04 ` Rafael J. Wysocki
2011-04-26 18:15 ` Dave Jones
2011-04-26 18:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
2011-04-29 20:15 ` Dave Jones
2011-04-30 0:05 ` Nicolas Pitre
2011-04-30 0:05 ` Nicolas Pitre
2011-08-13 15:46 ` [BUG?] Moving drivers to drivers/cpufreq/ causes all to be loaded Jonathan Nieder
2011-08-13 19:02 ` Jonathan Nieder
2011-08-13 21:11 ` Dave Jones
2011-08-14 0:18 ` Mattia Dongili
2011-08-14 0:18 ` Mattia Dongili
2011-08-14 17:01 ` Jonathan Nieder
2011-08-14 17:17 ` Kay Sievers
2011-08-14 17:17 ` Kay Sievers
2011-05-01 23:02 ` Status of arch/arm in linux-next Jamie Lokier
2011-05-01 23:02 ` Jamie Lokier
2011-04-19 16:27 ` Dave Jones
2011-04-19 16:27 ` Dave Jones
2011-04-19 17:12 ` Arnd Bergmann
2011-04-19 17:12 ` Arnd Bergmann
2011-04-20 6:36 ` Linus Walleij
2011-04-20 6:36 ` Linus Walleij
2011-04-21 7:32 ` Linus Walleij
2011-04-21 8:25 ` Arnd Bergmann
2011-04-22 7:56 ` Linus Walleij
2011-04-22 11:46 ` Linus Walleij
2011-05-02 13:49 ` Samuel Ortiz
2011-05-02 19:21 ` Linus Walleij
2011-04-20 7:33 ` Tony Lindgren
2011-04-20 7:43 ` Arnd Bergmann
2011-04-15 14:30 ` Martin Guy
2011-04-15 15:50 ` Russell King - ARM Linux
2011-04-18 15:17 ` Alexey Zaytsev
2011-04-18 16:23 ` Linus Torvalds
2011-04-18 21:54 ` Alexey Zaytsev
2011-04-19 15:02 ` Linus Torvalds
2011-04-19 15:20 ` Jean-Christophe PLAGNIOL-VILLARD
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=20110418081050.GG12272@atomide.com \
--to=tony@atomide.com \
--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.