linux-kernel - Re: [PATCH -tip] x86: thread_info.h moving comment to where it should be

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0907062052230.19480@localhost.localdomain>
Date:	Mon, 6 Jul 2009 20:54:46 +0200 (CEST)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
cc:	Christoph Lameter <cl@...ux-foundation.org>,
	David Howells <dhowells@...hat.com>,
	Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH -tip] x86: thread_info.h moving comment to where it should
 be

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/