The patch titled
     hard_smp_processor_id definition for UP systems without APIC (i386)
has been removed from the -mm tree.  Its filename was
     use-the-apic-to-determine-the-hardware-processor-id-i386-fix.patch

This patch was dropped because it was folded into 
use-the-apic-to-determine-the-hardware-processor-id-i386.patch

------------------------------------------------------
Subject: hard_smp_processor_id definition for UP systems without APIC (i386)
From: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>

Provide hard_smp_processor_id definition also for non apic case.

Signed-off-by: Fernando Luis Vazquez Cao <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
---

 include/asm-i386/smp.h |    8 ++++++++
 1 files changed, 8 insertions(+)

diff -puN 
include/asm-i386/smp.h~use-the-apic-to-determine-the-hardware-processor-id-i386-fix
 include/asm-i386/smp.h
--- 
a/include/asm-i386/smp.h~use-the-apic-to-determine-the-hardware-processor-id-i386-fix
+++ a/include/asm-i386/smp.h
@@ -90,6 +90,7 @@ extern unsigned int num_processors;
 #ifndef __ASSEMBLY__
 
 #ifdef CONFIG_X86_LOCAL_APIC
+
 #ifdef APIC_DEFINITION
 extern int hard_smp_processor_id(void);
 #else
@@ -100,6 +101,13 @@ static inline int hard_smp_processor_id(
        return GET_APIC_ID(*(unsigned long *)(APIC_BASE+APIC_ID));
 }
 #endif /* APIC_DEFINITION */
+
+#else /* CONFIG_X86_LOCAL_APIC */
+
+#ifndef CONFIG_SMP
+#define hard_smp_processor_id()                0
+#endif
+
 #endif /* CONFIG_X86_LOCAL_APIC */
 
 extern u8 apicid_2_node[];
_

Patches currently in -mm which might be from [EMAIL PROTECTED] are

remove-hardcoding-of-hard_smp_processor_id-on-up.patch
use-the-apic-to-determine-the-hardware-processor-id-i386.patch
use-the-apic-to-determine-the-hardware-processor-id-i386-fix.patch
use-the-apic-to-determine-the-hardware-processor-id-x86_64.patch
always-ask-the-hardware-to-obtain-hardware-processor.patch

-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to