public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: [PATCH] [0/8] Remove old deprecated x86 old machine check code & some cleanups
Date: Thu,  9 Jul 2009 00:31:36 +0200 (CEST)	[thread overview]
Message-ID: <200907091231.681564770@firstfloor.org> (raw)


This patchkit removes the old 32bit x86 machine check code. 
This was scheduled in feature-removal-schedule.txt for 2.6.32, so the
removal can be queued now.

Also a few minor fixes for issues I noticed while doing that.
They are all fairly harmless and more cleanups than real bug fixes.

And finally(mostly) addresses two of the left over review comments:
- moving the per bank state into a single structure. The CMCI ownership 
information is still separate for now because that would have needed more
restructuring, not appropiate for this "trivial" patch series
- centralize the calculation of MSR addresses

-Andi

             reply	other threads:[~2009-07-08 22:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 22:31 Andi Kleen [this message]
2009-07-08 22:31 ` [PATCH] [1/8] x86: mce: Make CONFIG_X86_ANCIENT_MCE dependent on CONFIG_X86_MCE Andi Kleen
2009-07-08 22:31 ` [PATCH] [2/8] x86: mce: Update X86_MCE description in x86/Kconfig Andi Kleen
2009-07-08 22:31 ` [PATCH] [3/8] x86: mce: Remove old i386 machine check code Andi Kleen
2009-07-08 22:31 ` [PATCH] [4/8] x86: mce: Rename CONFIG_X86_NEW_MCE to CONFIG_X86_MCE Andi Kleen
2009-07-08 22:31 ` [PATCH] [5/8] x86: mce: Move code in mce.c Andi Kleen
2009-07-08 22:31 ` [PATCH] [6/8] x86: mce: Move per bank data in a single datastructure Andi Kleen
2009-07-08 22:31 ` [PATCH] [7/8] x86: mce: macros to compute banks MSRs Andi Kleen
2009-07-08 22:31 ` [PATCH] [8/8] x86: mce: Lower maximum number of banks to architecture limit Andi Kleen

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=200907091231.681564770@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