mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Jaswinder Singh Rajput <jaswinder@kernel.org>
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] x86: thread_info.h moving comment to where it should be
Date: Mon, 6 Jul 2009 20:54:46 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LFD.2.00.0907062052230.19480@localhost.localdomain> (raw)
In-Reply-To: <1246879925.28541.3.camel@hpdv5.satnam>

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.

>  #define STACK_WARN	(THREAD_SIZE/8)
> +

How is that related ?

>  /*
>   * macros/functions for gaining access to the thread information structure
> - *
> - * preempt_count needs to be 1 initially, until the scheduler is functional.
>   */
>  #ifndef __ASSEMBLY__
>  
> -

Ditto.

Thanks,

	tglx

  reply	other threads:[~2009-07-06 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 11:32 Jaswinder Singh Rajput
2009-07-06 18:54 ` Thomas Gleixner [this message]
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
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=alpine.LFD.2.00.0907062052230.19480@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=jaswinder@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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

all inboxes | Powered by JetHome®