linux-kernel - Re: [PATCH] RT: fix spin_trylock

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: <alpine.LFD.0.9999.0710152308220.22612@localhost.localdomain>
Date:	Mon, 15 Oct 2007 23:35:43 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Daniel Walker <dwalker@...sta.com>
cc:	Steven Rostedt <rostedt@...dmis.org>,
	Sébastien Dugué <sebastien.dugue@...l.net>,
	Ingo Molnar <mingo@...e.hu>,
	Linux RT Users <linux-rt-users@...r.kernel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] RT: fix spin_trylock_irq

On Mon, 15 Oct 2007, Daniel Walker wrote:
> On Mon, 2007-10-15 at 14:14 -0400, Steven Rostedt wrote:
> 
> > > This is the second fix for this .. The first was in this email (over a
> > > month ago)
> > >
> > > http://lkml.org/lkml/2007/8/31/318
> > 
> > You're right I missed that. (I even read it). But for fixes like this, (or
> > any patches that are not in the tree), you really need to resend the
> > series.
> 
> In hindsight I should have resent, but I didn't .. Really it's a matter
> of frustration on my part. Where I submit patches that should be
> included , but they are ignored for no clear reason .. Then I submit
> again, and the patches are ignored again for no clear reason..

You were asked to rebase your patches against the latest -rt
kernel. And you bluntly refused to.

I knew exactly why I ignored the patches when I was moving -rt
forward. Simply because I had not enough time to review them in
detail. Ingo acked them in principle, but we had subtle wreckage from
such changes before and I had no intention to put more risk into a non
trivial merge.

Sorry, you have provided sloppy patches more than once and requested
us to pick random bugfixes from a broken ftp server or from the
mailing list. It's you who wrote the track record, not us.

I'm finally fed up with your prima ballerina attitudes. Either you
want to be part of this project or not. If yes, then please accept
that you are not setting the rules how this works. If no, please stop
whining at us and look for a nice sandpit where you can play these
silly games.

	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/