From: Jaswinder Singh Rajput <jaswinder@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Christoph Lameter <cl@linux-foundation.org>,
David Howells <dhowells@redhat.com>, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
x86 maintainers <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -tip V2] x86: thread_info.h moving comment to where it should be
Date: Tue, 07 Jul 2009 10:51:28 +0530 [thread overview]
Message-ID: <1246944088.2422.10.camel@ht.satnam> (raw)
In-Reply-To: <alpine.LFD.2.00.0907062321370.19480@localhost.localdomain>
On Tue, 2009-07-07 at 00:44 +0200, Thomas Gleixner wrote:
> Jaswinder,
>
> On Tue, 7 Jul 2009, Jaswinder Singh Rajput wrote:
> > On Mon, 2009-07-06 at 20:54 +0200, Thomas Gleixner wrote:
> > > On Mon, 6 Jul 2009, Jaswinder Singh Rajput wrote:
> > > >
> > > > By mistake commit 2052e8d40ad58 moved following comment to wrong place,
> > > > where it does not make any sense :
> > >
> > > Wrong. commit 2052e8d4 had the comments in the right place. commit
> > > 3351cc03 replaced the two identical INIT_THREAD_INFO macros and did
> > > not update the comments.
> > >
> >
> > Ahh so you was also part of it, here is updated patch:
>
> if you expect that you earn more trust by such snotty comments, then
> you are really on the wrong track. To keep the record straight:
>
You started it and when it comes to you why you start jumping.
> _You_ sent a patch with a bogus patch description.
>
Have you applied it or you only shouts like always.
--
JSR
next prev parent reply other threads:[~2009-07-07 5:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 11:32 [PATCH -tip] x86: thread_info.h moving comment to where it should be Jaswinder Singh Rajput
2009-07-06 18:54 ` Thomas Gleixner
2009-07-06 21:05 ` [PATCH -tip V2] " Jaswinder Singh Rajput
2009-07-06 22:44 ` Thomas Gleixner
2009-07-07 5:21 ` Jaswinder Singh Rajput [this message]
2009-07-07 16:15 ` Christoph Lameter
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=1246944088.2422.10.camel@ht.satnam \
--to=jaswinder@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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