safe_smp_processor_id i386 and x86_64

I was looking at the git log and the below changes confused me.

dc2bc768a009b9ad8711894c544dc6b0d8c0ce57

commit dc2bc768a009b9ad8711894c544dc6b0d8c0ce57
Author: Fernando Vazquez <[email protected]>
Date:   Sat Sep 30 23:29:07 2006 -0700

   [PATCH] stack overflow safe kdump: safe_smp_processor_id()

..............

  This patch set does the following:

   * Add safe_smp_processor_id function to i386 architecture (this function was
     inspired by the x86_64 function of the same name).

151f8cc1169f9052095b2be36183ab132d75c6c2

commit 151f8cc1169f9052095b2be36183ab132d75c6c2
Author: Andi Kleen <[email protected]>
Date:   Tue Sep 26 10:52:37 2006 +0200

   [PATCH] Remove safe_smp_processor_id()




-aneesh

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: safe_smp_processor_id i386 and x86_64
    • From: [email protected] (Eric W. Biederman)

• Prev by Date: [patch] honour MNT_NOEXEC for access()
• Next by Date: Re: 2.6.19-rc1 genirq causes either boot hang or "do_IRQ: cannot handle IRQ -1"
• Previous by thread: [PATCH 2.6.19-git] Fix ARM breakage due to no irq_regs.h
• Next by thread: Re: safe_smp_processor_id i386 and x86_64
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]