From: Andi Kleen <ak@linux.intel.com>
To: hpa@zytor.com, mingo@redhat.com, torvalds@linux-foundation.org,
ak@linux.intel.com, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: [tip:x86/urgent] x86, mce: remove incorrect __cpuinit for mce_cpu_features()
Date: Sun, 22 Feb 2009 12:59:18 +0100 [thread overview]
Message-ID: <49A13E16.5030401@linux.intel.com> (raw)
In-Reply-To: <tip-cc3ca22063784076bd240fda87217387a8f2ae92@kernel.org>
H. Peter Anvin wrote:
> Author: H. Peter Anvin <hpa@zytor.com>
> AuthorDate: Fri, 20 Feb 2009 23:35:51 -0800
> Commit: H. Peter Anvin <hpa@zytor.com>
> CommitDate: Fri, 20 Feb 2009 23:40:40 -0800
>
> x86, mce: remove incorrect __cpuinit for mce_cpu_features()
>
> Impact: Bug fix on UP
Thanks!
> Remove the offending __cpuinit annotations for mce_cpu_features() and
> its successor functions.
>
> Cc: Andi Kleen <ak@linux.intel.com>
> Cc: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: H. Peter Anvin <hpa@zytor.com>
Acked-by: Andi Kleen <ak@linux.intel.com>
-Andi
parent reply other threads:[~2009-02-22 11:59 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <tip-cc3ca22063784076bd240fda87217387a8f2ae92@kernel.org>]
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=49A13E16.5030401@linux.intel.com \
--to=ak@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox