[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1246879925.28541.3.camel@hpdv5.satnam>
Date: Mon, 06 Jul 2009 17:02:05 +0530
From: Jaswinder Singh Rajput <jaswinder@...nel.org>
To: 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: [PATCH -tip] x86: thread_info.h moving comment to where it should
be
By mistake commit 2052e8d40ad58 moved following comment to wrong place,
where it does not make any sense :
"preempt_count needs to be 1 initially, until the scheduler is functional."
Moving comment back to right place where preempt_count is setting to 1
Signed-off-by: Jaswinder Singh Rajput <jaswinderrajput@...il.com>
---
arch/x86/include/asm/thread_info.h | 8 ++++----
1 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/x86/include/asm/thread_info.h b/arch/x86/include/asm/thread_info.h
index b078352..2dda0f8 100644
--- a/arch/x86/include/asm/thread_info.h
+++ b/arch/x86/include/asm/thread_info.h
@@ -43,6 +43,9 @@ struct thread_info {
int uaccess_err;
};
+/*
+ * preempt_count needs to be 1 initially, until the scheduler is functional.
+ */
#define INIT_THREAD_INFO(tsk) \
{ \
.task = &tsk, \
@@ -167,14 +170,12 @@ struct thread_info {
#ifdef CONFIG_X86_32
#define STACK_WARN (THREAD_SIZE/8)
+
/*
* macros/functions for gaining access to the thread information structure
- *
- * preempt_count needs to be 1 initially, until the scheduler is functional.
*/
#ifndef __ASSEMBLY__
-
/* how to get the current stack pointer from C */
register unsigned long current_stack_pointer asm("esp") __used;
@@ -205,7 +206,6 @@ static inline struct thread_info *current_thread_info(void)
/*
* macros/functions for gaining access to the thread information structure
- * preempt_count needs to be 1 initially, until the scheduler is functional.
*/
#ifndef __ASSEMBLY__
DECLARE_PER_CPU(unsigned long, kernel_stack);
--
1.6.0.6
--
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/
Powered by blists - more mailing lists