Messages in this thread Patch in this message | | | Date | Wed, 4 Aug 2004 21:48:39 -0700 | From | William Lee Irwin III <> | Subject | [sparc32] [7/13] remove references to num_context_patch2 |
| |
On Wed, Aug 04, 2004 at 09:47:36PM -0700, William Lee Irwin III wrote: > This looks rather unusual, however, this is what sparc32 really wants. > The function pointer argument to kernel_thread() is irrelevant here; > the execution state of the thread is established in the SMP trampoline.
num_context_patch2 is never defined, only declared. However, these declarations generate an undefined symbol reference. So remove it.
Index: mm2-2.6.8-rc2/arch/sparc/kernel/entry.S =================================================================== --- mm2-2.6.8-rc2.orig/arch/sparc/kernel/entry.S +++ mm2-2.6.8-rc2/arch/sparc/kernel/entry.S @@ -858,7 +858,7 @@ vac_hwflush_patch2_on: sta %g0, [%l3 + %l7] ASI_HWFLUSHSEG .globl invalid_segment_patch1, invalid_segment_patch2 - .globl num_context_patch1, num_context_patch2 + .globl num_context_patch1 .globl vac_linesize_patch, vac_hwflush_patch1 .globl vac_hwflush_patch2 Index: mm2-2.6.8-rc2/arch/sparc/mm/sun4c.c =================================================================== --- mm2-2.6.8-rc2.orig/arch/sparc/mm/sun4c.c +++ mm2-2.6.8-rc2/arch/sparc/mm/sun4c.c @@ -379,7 +379,7 @@ extern unsigned long invalid_segment_patch2, invalid_segment_patch2_ff; extern unsigned long invalid_segment_patch1_1ff, invalid_segment_patch2_1ff; extern unsigned long num_context_patch1, num_context_patch1_16; -extern unsigned long num_context_patch2, num_context_patch2_16; +extern unsigned long num_context_patch2_16; extern unsigned long vac_linesize_patch, vac_linesize_patch_32; extern unsigned long vac_hwflush_patch1, vac_hwflush_patch1_on; extern unsigned long vac_hwflush_patch2, vac_hwflush_patch2_on; - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |