[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1210039855.17132.105.camel@localhost.localdomain>
Date: Mon, 05 May 2008 19:10:55 -0700
From: Daniel Walker <dwalker@...sta.com>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Sven-Thorsten Dietrich <sven@...bigcorporation.com>,
Remy Bohmer <linux@...mer.net>,
LKML <linux-kernel@...r.kernel.org>,
RT <linux-rt-users@...r.kernel.org>,
Jon Masters <jonathan@...masters.org>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: Preempt-RT patch for 2.6.25
On Tue, 2008-05-06 at 03:54 +0200, Thomas Gleixner wrote:
> On Mon, 5 May 2008, Daniel Walker wrote:
> > On Mon, 2008-05-05 at 23:01 +0200, Thomas Gleixner wrote:
> > > We have been there before. kernel development does not follow the "we
> > > want _now_" principle at all. Have you ever tried to yell at Linus "we
> > > want XYZ _now_" ? If you decide to try it, please keep me on CC - I
> > > want to enjoy the show.
> >
> > Kernel development is "What is available now?" not what is avaiable in
> > the future.
> >
> > If you want to reject code you better have a reason other than "We're
> > going to make some new code for that (some time in the future) sorry."
>
> You miss the point. We reject code which breaks existing functionality.
This point , to me, isn't valid. Even if you think it is, the point was
brought up just recently, after Steven finish port to 2.6.25.
So assuming you think bisection is good, and you think the architectures
should have been included then we should have discussed it a long time
ago when my code was first release.
It's not like -rt is overflowing with patches to evaluate.
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists