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]

Message-Id: <1210089663.17132.128.camel@localhost.localdomain>
Date:	Tue, 06 May 2008 09:01:03 -0700
From:	Daniel Walker <dwalker@...sta.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Thomas Gleixner <tglx@...utronix.de>,
	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>
Subject: Re: Preempt-RT patch for 2.6.25


On Tue, 2008-05-06 at 10:43 +0200, Ingo Molnar wrote:
> * Daniel Walker <dwalker@...sta.com> wrote:
> 
> > > Since it's code that you regard stale it shouldnt be all that hard 
> > > to fix it up - in general it's much easier to fix a bug than to talk 
> > > it out of existence, even if you disagree with a maintainer about 
> > > how significant a bug is.
> > 
> > It shouldn't be hard, but it's too much to do all in one go. [...]
> 
> this sort of "it was too hard for me but I expect the maintainers to 
> clean up the mess" stance, combined with an aggressive, uncompromising, 
> demanding tone towards the maintainers of a project wont get you very 
> far in contributing to any open-source project. You are not their boss, 
> you have to learn to work with them instead of trying to force your 
> opinion on them. They clearly try to work with you and gave a 
> straightforward technical description of how your contribution would be 
> acceptable to the project. All the rest is just a waste of everyone's 
> time that could be better spent on improving the project. JFYI.

It's not "too hard for me" it's a matter of correctness. As if I would
ever say that Ingo ..

I'm not forcing my opinion on anyone. I'm assuming cleanup are
acceptable, especially bisect cleanup (when your code isn't bisectable).
My position is based on that.

You release a dirty -rt tree and expect no one will clean it up, and
further more if they do clean up your code you just toss the work aside
like it's pointless. I take it you don't want clean ups. From my
perspective you should be thanking me.

Had Steven simple said "Please include all the architecture" a month ago
when I released my code, I may have actually done that.

This thread is in no way a plea to get my code included. My code never
had a chance to be included anyway ..

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/