lkml.org 
[lkml]   [2006]   [Jan]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Development tree, PLEASE?


--On January 20, 2006 11:17:57 PM +0000 Russell King
<rmk+lkml@arm.linux.org.uk> wrote:

> On Fri, Jan 20, 2006 at 01:56:12PM -0700, Michael Loftis wrote:
>> A decent amount of ARM stuff moving around between even just 2.6.11
>> and 2.6.13 (admittedly that's a gripe for ARM) making development for
>> that port very painful
>
> What you're complaining about here seems to be:
>
> 1. the cleanup of the entry and debug code - TRIVIAL - it's a
> cut-n-paste job. No interface change. Estimated time to
> resolve: 5 minutes
> 2. moving the machine specific boot makefile parameters into
> arch/arm/mach-* - TRIVIAL - it's a cut-n-paste job. No interface
> change. Estimated time to resolve: 5 minutes.
> 3. removing messy macros for the machine description. Slightly less
> trivial because you need to do some investigation and then an
> exercise of about 10 subsitutions in one file. Estimated time
> to resolve: 30 minutes.
>
> All changes listed above to lower the long term maintainence burden of
> the kernel _and_ make it easier to port to new SoCs.
>
> Ok, so, let's be generous - call it one hour. Are you _really_ griping
> about one hour's work on your part being "very painful"?

As long as it isn't wash rinse repeat, but in development kernels it tends
to be. That's the pain point. It's not one single huge problem, it's the
constant stream of little ones that we try to avoid.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2006-01-21 00:36    [W:0.205 / U:0.052 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site