From: Thomas Gleixner <tglx@linutronix.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: mingo@redhat.com, hpa@zytor.com, linux-kernel@vger.kernel.org,
henrix@sapo.pt, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:irq/genirq] genirq: do not execute DEBUG_SHIRQ when irq setup failed
Date: Thu, 2 Apr 2009 18:38:22 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0904021831470.12916@localhost.localdomain> (raw)
In-Reply-To: <1238689216.3099.34.camel@ht.satnam>
On Thu, 2 Apr 2009, Jaswinder Singh Rajput wrote:
>
> I am dead sure, you really need some good manners and need to learn many
> things.
Ok. Now it's definitly enough.
You started yelling at the patch submitter in an unfriendly and
totally unjustified way. And your analysis of the patch was completely
wrong as well.
I pointed that out to you and instead of thinking for a minute you
insist on your completely wrong analysis and tell me another time
about the code which I know probably better than most of the kernel
hackers.
The question arises who needs manners and who needs to learn things.
tglx
next prev parent reply other threads:[~2009-04-02 16:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-01 17:06 [RESEND][PATCH -tip] irq: DEBUG_SHIRQ executed on irq setup failure Luis Henriques
2009-04-02 14:03 ` [tip:irq/genirq] genirq: do not execute DEBUG_SHIRQ when irq setup failed Luis Henriques
2009-04-02 14:32 ` Jaswinder Singh Rajput
2009-04-02 15:21 ` Thomas Gleixner
2009-04-02 15:41 ` Jaswinder Singh Rajput
2009-04-02 16:08 ` Thomas Gleixner
2009-04-02 16:20 ` Jaswinder Singh Rajput
2009-04-02 16:38 ` Thomas Gleixner [this message]
2009-04-02 16:45 ` Jaswinder Singh Rajput
2009-04-02 17:16 ` Luis Henriques
2009-04-02 17:32 ` Ingo Molnar
2009-04-02 17:46 ` Jaswinder Singh Rajput
2009-04-02 18:01 ` Ingo Molnar
2009-04-23 6:48 ` tip-bot for Luis Henriques
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=alpine.LFD.2.00.0904021831470.12916@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=henrix@sapo.pt \
--cc=hpa@zytor.com \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@redhat.com \
/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
all inboxes | Powered by JetHome®