Re: Preempt-RT patch for 2.6.25

[Daniel Walker]

On Mon, 2008-05-05 at 12:44 -0400, Steven Rostedt wrote:
> On Mon, 5 May 2008, Daniel Walker wrote:
> >
> > You should review my tree, it is several steps closer to mainline that
> > the -rt version your working on. I did a lot of patch break-ups
> > (required for bisection, and makes for a cleaner tree) and re-arranging
> > patches.
> 
> I may take a look at your tree. But as for the rt version I'm working on,
> is not the same as the one you started with. I did a lot of merging, I
> also have the new ftrace code in there. I also moved patches around to
> what we will be pushing to mainline.

That's really the point, you should have started with my version. I
released my changes long before the 2.6.25 release.

> >
> > Bisection is also required for mainline integration ..
> 
> Bisection is required for each element, we don't need it for the entire
> tree (atm). If we waste our time making the entire tree fully bisectable,
> then it will be a lot of work to maintain that bisectability when we
> rewrite entire sections.

Bisection is required for everything, every patch. I am giving you a
bisect tree, there is no time wasted (only mine)..

I'm not following your logic Steven .. You want bisection , that means
you should want to maintain it, and write code in the future which also
bisects.

If someone submits code which doesn't bisect you kick it the same way
it's kicked from mainline. That means future patches in -rt are ready
for mainline which helps further the goal of mainline integration.

> I am making it boot with certain parts intergrated. But my goal is not to
> have every single patch compile and boot. We'll worry about that when we
> need to push a part of the code in. But reality, what is there now, I can
> guarantee will not be the code that is pushed when it is ready.

What you guarantee to happen in the future is irrelevant .. We want
bisection _now_ , not months from now..

Bisection has lots of benefits, it's not just that one stupid
requirement mainline has and no one really cares about.

Daniel

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