From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: virtualization@lists.osdl.org,
Andrew Morton <akpm@linux-foundation.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO
Date: Fri, 06 Apr 2007 15:41:52 -0700 [thread overview]
Message-ID: <20070406224152.556848893@goop.org> (raw)
Hi Andi,
Four patches:
- clean up asm/bugs.h, by moving all the C code into its own C file
- split identify_cpu() into boot and secondary variants, so that
boot-time setup functions can be marked __init
- repost of the COMPAT_VDSO patches with a bit more robustness from
unknown DT_tags, and functions marked __init, since all this is
boot-time only setup.
Thanks,
J
--
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
virtualization@lists.osdl.org,
lkml <linux-kernel@vger.kernel.org>
Subject: [patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO
Date: Fri, 06 Apr 2007 15:41:52 -0700 [thread overview]
Message-ID: <20070406224152.556848893@goop.org> (raw)
Hi Andi,
Four patches:
- clean up asm/bugs.h, by moving all the C code into its own C file
- split identify_cpu() into boot and secondary variants, so that
boot-time setup functions can be marked __init
- repost of the COMPAT_VDSO patches with a bit more robustness from
unknown DT_tags, and functions marked __init, since all this is
boot-time only setup.
Thanks,
J
--
next reply other threads:[~2007-04-06 22:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-06 22:41 Jeremy Fitzhardinge [this message]
2007-04-06 22:41 ` [patch 0/4] Clean up asm/bugs.h, identify_cpu() and update COMPAT_VDSO Jeremy Fitzhardinge
2007-04-06 22:41 ` [patch 1/4] Clean up asm-i386/bugs.h Jeremy Fitzhardinge
2007-04-06 22:41 ` Jeremy Fitzhardinge
2007-04-06 22:41 ` [patch 2/4] clean up identify_cpu Jeremy Fitzhardinge
2007-04-06 22:41 ` Jeremy Fitzhardinge
2007-04-07 9:14 ` Andrew Morton
2007-04-07 9:14 ` Andrew Morton
2007-04-07 17:20 ` Jeremy Fitzhardinge
2007-04-07 17:20 ` Jeremy Fitzhardinge
2007-04-07 17:59 ` Andrew Morton
2007-04-07 18:39 ` Sam Ravnborg
2007-04-07 18:39 ` Sam Ravnborg
2007-04-07 19:06 ` Andrew Morton
2007-04-06 22:41 ` [patch 3/4] Relocate VDSO ELF headers to match mapped location with COMPAT_VDSO Jeremy Fitzhardinge
2007-04-06 22:41 ` Jeremy Fitzhardinge
2007-04-06 22:41 ` [patch 4/4] Make COMPAT_VDSO runtime selectable Jeremy Fitzhardinge
2007-04-06 22:41 ` Jeremy Fitzhardinge
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=20070406224152.556848893@goop.org \
--to=jeremy@goop.org \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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.