From: jayakumar.lkml@gmail.com (Jaya Kumar)
To: linux-arm-kernel@lists.infradead.org
Subject: Updated mach-types update
Date: Tue, 24 May 2011 19:00:05 +0800 [thread overview]
Message-ID: <BANLkTi=esTs+gTxGqbZc+TJgcna5OtmWhA@mail.gmail.com> (raw)
In-Reply-To: <201105231839.57083.arnd@arndb.de>
On Tue, May 24, 2011 at 12:39 AM, Arnd Bergmann <arnd@arndb.de> wrote:
>
> We need to do more of those before we see significant reductions from
> being able to remove a lot of the existing board files. At the same
> time, a number of people obviously have new boards that they want to
> see supported. The tactical answer that I'd give to them is that they
> can still add board files, provided that they also help do the work
> that is required to remove them later (depends the specific capabilities
> of the people and the complexity of the code they want to add).
Hi Arnd,
Thanks for the feedback. I think this thread went from the specific
case of this 2363, Wayland board into a broader discussion. I
understand this is because of the arm subarch cleanup goals. To help
people like me who aren't familiar with the details, could you
elaborate on "can still add board files" and "the work that is
required to remove them later". Do you mean I could still submit a
patch like arch/arm/mach-mmp/wayland* and you'd be willing to take it,
but with the expectation that it would be removed at a later date? Is
the removal work to do with adding device tree support (I assume
that's a bootloader task as well as a subarch/board support task)? I'm
happy to help with what I can but I'm very slow. I'm even having
trouble just getting mainline to boot on the board. [1]
Thanks,
jaya
[1] http://www.spinics.net/lists/arm-kernel/msg125769.html
next prev parent reply other threads:[~2011-05-24 11:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-20 11:03 Updated mach-types update Russell King - ARM Linux
2011-03-20 11:41 ` Russell King - ARM Linux
2011-03-24 17:59 ` Tony Lindgren
2011-05-13 11:54 ` Tony Lindgren
2011-05-13 12:19 ` Jarkko Nikula
2011-05-13 14:40 ` [PATCH] omap: Remove support for omap2evm (Re: Updated mach-types update) Tony Lindgren
2011-05-14 16:30 ` Mark Brown
2011-05-16 13:45 ` Liam Girdwood
2011-05-13 14:53 ` Updated mach-types update Tomi Valkeinen
2011-03-21 22:41 ` Detlef Vollmann
2011-03-21 23:10 ` Russell King - ARM Linux
2011-03-21 23:33 ` Detlef Vollmann
2011-03-22 13:19 ` Domenico Andreoli
2011-03-22 19:30 ` Russell King - ARM Linux
2011-03-23 9:31 ` Domenico Andreoli
2011-03-23 16:37 ` H Hartley Sweeten
2011-03-26 22:52 ` Colin Cross
2011-03-26 23:14 ` Russell King - ARM Linux
2011-03-28 18:00 ` Russell King - ARM Linux
2011-03-28 18:02 ` Russell King - ARM Linux
2011-05-21 1:35 ` Jaya Kumar
2011-05-22 9:11 ` Russell King - ARM Linux
2011-05-23 14:52 ` Arnd Bergmann
2011-05-23 14:59 ` Russell King - ARM Linux
2011-05-23 15:10 ` Mark Brown
2011-05-23 15:33 ` Russell King - ARM Linux
2011-05-23 16:39 ` Arnd Bergmann
2011-05-24 11:00 ` Jaya Kumar [this message]
2011-05-24 11:51 ` Arnd Bergmann
2011-07-27 12:20 ` Mark Brown
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='BANLkTi=esTs+gTxGqbZc+TJgcna5OtmWhA@mail.gmail.com' \
--to=jayakumar.lkml@gmail.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 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).