linux-kernel - Re: Preempt-RT patch for 2.6.25

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 May 2008 10:19:22 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Daniel Walker <dwalker@...sta.com>
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 Mon, 5 May 2008, Daniel Walker wrote:
> 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.

Even if you don't care to put me on CC I pretty much follow the
mailing list. All I can see is your priggish "release" message, but no
sign of prior discussion on how to approach that problem.

> 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.

You have "released" code and trees before which were ignored. All for
the same reason: your unwillingness to cooperate.

You create some "works for me" artifact, "release" it pompously and
expect that it is picked up and the work you were not willing to do is
finished by others. If that's not happening then you waste everyones
valuable time with your brashly impertinent and stubborn requests to
enforce your POV on those who have developed and maintained preempt-rt
for years.

If that is your idea of cooperation then please look for a community
and maintainers who are willing to accept that mode of operation.

Thanks,

	tglx
--
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/