From: Andi Kleen <andi@firstfloor.org>
To: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] [2/4] MCE: Add old machine check code to feature-removal-schedule.txt
Date: Tue, 5 Aug 2008 19:17:36 +0200 (CEST) [thread overview]
Message-ID: <20080805171736.6CFC21B90084@one.firstfloor.org> (raw)
In-Reply-To: <20080805717.971524000@firstfloor.org>
Signed-off-by: Andi Kleen <ak@linux.intel.com>
Index: linux/Documentation/feature-removal-schedule.txt
===================================================================
--- linux.orig/Documentation/feature-removal-schedule.txt
+++ linux/Documentation/feature-removal-schedule.txt
@@ -321,3 +321,13 @@ Why: This option was introduced just to
to keep working over the upgrade to 2.6.26. At the scheduled time of
removal fixed lm-sensors (2.x or 3.x) should be readily available.
Who: Rene Herman <rene.herman@gmail.com>
+
+----------------------------
+
+What: CONFIG_X86_OLD_MCE
+When: 2.6.29
+Why: Remove the old legacy 32bit machine check code. This has been superseded
+ by the 64bit machine check code, but the old version has been kept
+ around for easier testing. Note this doesn't impact the old P5 and WinChip
+ machine check handlers.
+Who: Andi Kleen <ak@linux.intel.com>
next prev parent reply other threads:[~2008-08-05 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 17:17 [PATCH] [0/4] Updates to the x86 machine check unification Andi Kleen
2008-08-05 17:17 ` [PATCH] [1/4] MCE: Fix ifdefs for Intel thermal handler Andi Kleen
2008-08-05 17:17 ` Andi Kleen [this message]
2008-08-05 17:17 ` [PATCH] [3/4] MCE: Reinitialize per cpu features and ancient mces on resume Andi Kleen
2008-08-05 17:17 ` [PATCH] [4/4] MCE: Don't disable machine checks during code patching Andi Kleen
2008-08-08 22:23 ` [PATCH] [0/4] Updates to the x86 machine check unification H. Peter Anvin
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=20080805171736.6CFC21B90084@one.firstfloor.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®