All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: safe_smp_processor_id i386 and x86_64
Date: Fri, 06 Oct 2006 22:02:17 +0530	[thread overview]
Message-ID: <eg60ej$qqe$1@sea.gmane.org> (raw)

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

dc2bc768a009b9ad8711894c544dc6b0d8c0ce57

commit dc2bc768a009b9ad8711894c544dc6b0d8c0ce57
Author: Fernando Vazquez <fernando@intellilink.co.jp>
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 <ak@suse.de>
Date:   Tue Sep 26 10:52:37 2006 +0200

    [PATCH] Remove safe_smp_processor_id()




-aneesh


             reply	other threads:[~2006-10-06 18:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 16:32 Aneesh Kumar K.V [this message]
2006-10-11 16:58 ` safe_smp_processor_id i386 and x86_64 Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='eg60ej$qqe$1@sea.gmane.org' \
    --to=aneesh.kumar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.