From: Steven Rostedt <rostedt@goodmis.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Hillf Danton <dhillf@gmail.com>,
LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] sched: correct testing need_resched in mutex_spin_on_owner()
Date: Tue, 7 Jun 2011 11:43:02 -0400 [thread overview]
Message-ID: <20110607154302.GD27245@home.goodmis.org> (raw)
In-Reply-To: <1307460040.2322.279.camel@twins>
On Tue, Jun 07, 2011 at 05:20:40PM +0200, Peter Zijlstra wrote:
>
> Please, get a grip on reality and stop sending endless streams of
> patches based on wrong assumptions and mis-understandings.
Hillf,
Some of your patches are good, but others are frivolous. It becomes a
burden on the maintainer to figure out which is which.
I've asked you to please back up your patches with tests and/or
benchmarks that clearly demonstrate what you are showing. I have yet to
see any of that. If you have trouble coming up with test cases it may be
because your assumptions about what is happening is incorrect.
If you just randomly send out a bunch of patches where the noise/signal
ratio is high, you will soon just be ignored. I don't want this
happening, as I stated, some of your patches are good. But when you
start to fight back and it becomes clear that you totally do not
understand what you are talking about, it becomes hard to take you
seriously.
-- Steve
prev parent reply other threads:[~2011-06-07 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-07 13:41 Hillf Danton
2011-06-07 13:47 ` Peter Zijlstra
2011-06-07 13:50 ` Peter Zijlstra
2011-06-07 13:59 ` Peter Zijlstra
2011-06-07 14:14 ` Hillf Danton
2011-06-07 14:10 ` Hillf Danton
2011-06-07 14:24 ` Peter Zijlstra
2011-06-07 14:36 ` Hillf Danton
2011-06-07 14:40 ` Peter Zijlstra
2011-06-07 14:47 ` Hillf Danton
2011-06-07 15:08 ` Steven Rostedt
2011-06-07 18:22 ` Hillf Danton
2011-06-07 18:34 ` Steven Rostedt
2011-06-07 15:20 ` Peter Zijlstra
2011-06-07 15:43 ` Steven Rostedt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110607154302.GD27245@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=dhillf@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome