lkml.org 
[lkml]   [2005]   [Mar]   [4]   [last100]   RSS Feed
Views: [more markup]   [less markup]   [headers]   [forward]  
 
Messages in this thread
/
DateThu, 3 Mar 2005 22:20:15 -0800
FromAndrew Morton <>
SubjectRe: [PATCH] trivial fix for 2.6.11 raid6 compilation on ppc w/ Altivec
Jeff Garzik <jgarzik@pobox.com> wrote:
>
> > Neither solution is acceptable, really.  I suspect the idea of pulling
>  > linux-release into mainline won't work very well, and that making it a
>  > backport tree would be more practical.
> 
>  Maybe you're right, but I tend to think that "quick, get that fix out 
>  immediately" fixes will appear before more substantial fixes.  That is 
>  certainly the way things have worked up until now.
> 
>  For the cases that we care about, putting that into linux-release and 
>  then pulling would seem more appropriate.
> 
>  Remember, the linux-release tree for each release will slow down, and 
>  eventually die off, as we progress towards the next release (where the 
>  linux-2.6.x.y-1 tree will indeed die).

Yup.  But anyway, there's no point in overdesigning all this.  Let's suck
it and see.  If it doesn't work we can populate linux-release by some other
means.  The downstream users of linux-release won't see any change as a
result of that.

-
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: 2005-03-22 13:10    [W:0.188 / U:0.270 seconds]
©2003-2008 Jasper Spaans