From: Daniel Walker <dwalker@mvista.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: v2.6.21-rt3
Date: Tue, 22 May 2007 08:20:09 -0700 [thread overview]
Message-ID: <1179847209.15427.75.camel@imap.mvista.com> (raw)
In-Reply-To: <20070522082550.GA8161@elte.hu>
On Tue, 2007-05-22 at 10:25 +0200, Ingo Molnar wrote:
> * Daniel Walker <dwalker@mvista.com> wrote:
>
> > I copied the patch into the first email, I did look at it which is why
> > you got an email. Your introducing the patch , it's for you to explain
> > why it needs to be there.. considering that the comment says "hack" in
> > it, I have to wonder what the non-hack version is ..
>
> you might not have realized it, but the problem i think was the attitude
> you showed in the very first sentence:
I was not intending any attitude. I had no idea where those changes came
from ..
> > Where did the arm ep93xx changes come from? It looks like patch below
> > came in with them in 2.6.21-rt6 ..
>
> AFAICS Thomas just mirrored that snotty comment back to you, and yes,
> when you are on the receiving end it feels nasty, doesnt it? So please
> restart and rephrase that into a more polite form and you might get an
> answer (although i certainly do not talk for Thomas). Something like:
I don't read the sentence you quoted as snotty at all .. I had no idea
where the changes came from, and I was simply asking that.. Since there
isn't a history for the -rt patch, I honestly don't know where some of
the code comes from ..
Since I had no idea that Thomas wrote that code, there's no premeditated
aggravation, or flame bait there..
> > Thomas, could you give me a bit more information about why the arm
> > ep93xx changes were done in 2.6.21-rt6? I do not seem to understand
> > the reason behind that change. I've attached the change below. Thanks!
>
> You are asking Thomas a favor after all... Be a bit more polite when
> asking others, and a completely new world might open up for you :-)
I don't see that as me asking a favor.. If a patch crosses LKML and I
ask "Why does this hunk exist?" that's not a favor. That is pure code
review, which is exactly what I was doing in this thread. Which is
reviewing code and asking questions..
I hope you don't read my comments above as snotty cause it's not suppose
to be, just conversation..
Daniel
prev parent reply other threads:[~2007-05-22 15:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-17 19:41 v2.6.21-rt3 Ingo Molnar
2007-05-18 7:39 ` v2.6.21-rt3 emin ak
2007-05-18 7:53 ` v2.6.21-rt3 Thomas Gleixner
2007-05-18 8:10 ` v2.6.21-rt3 emin ak
2007-05-18 8:31 ` v2.6.21-rt3 Thomas Gleixner
2007-05-18 8:52 ` v2.6.21-rt3 Wolfgang Grandegger
2007-05-21 16:04 ` v2.6.21-rt3 K.R. Foley
2007-05-21 20:11 ` v2.6.21-rt3 Daniel Walker
2007-05-21 20:24 ` v2.6.21-rt3 Thomas Gleixner
2007-05-21 20:25 ` v2.6.21-rt3 Daniel Walker
2007-05-21 20:36 ` v2.6.21-rt3 Thomas Gleixner
2007-05-21 20:41 ` v2.6.21-rt3 Daniel Walker
2007-05-22 8:25 ` v2.6.21-rt3 Ingo Molnar
2007-05-22 15:20 ` Daniel Walker [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=1179847209.15427.75.camel@imap.mvista.com \
--to=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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