From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>
Subject: [GIT PULL] x86/cpu changes for v3.12
Date: Tue, 3 Sep 2013 16:51:18 +0200 [thread overview]
Message-ID: <20130903145118.GA29006@gmail.com> (raw)
Linus,
Please pull the latest x86-cpu-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-cpu-for-linus
HEAD: 237d1548543312fcc8c99d302ab68fbf8ef6f97f x86: Fix override new_cpu_data.x86 with 486
Two small cpufeature support updates.
[ NOTE: diffstat was created manually. ]
Thanks,
Ingo
------------------>
Borislav Petkov (1):
x86, cpufeature: Use new CC_HAVE_ASM_GOTO
H. Peter Anvin (1):
Merge remote-tracking branch 'origin/x86/fpu' into queue/x86/cpu
Wang YanQing (1):
x86: Fix override new_cpu_data.x86 with 486
Merge made by the 'recursive' strategy.
arch/x86/include/asm/cpufeature.h | 17 +++++++++++------
arch/x86/kernel/head_32.S | 2 +-
2 files changed, 12 insertions(+), 7 deletions(-)
reply other threads:[~2013-09-03 14:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20130903145118.GA29006@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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.