public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: linux-kernel@vger.kernel.org, JBottomley@parallels.com,
	Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org
Subject: Re: [PATCH 5/5] MCA: delete all remaining traces of microchannel bus support.
Date: Thu, 17 May 2012 20:00:01 +0200	[thread overview]
Message-ID: <20120517180001.GA17846@gmail.com> (raw)
In-Reply-To: <1337272841-25931-6-git-send-email-paul.gortmaker@windriver.com>


* Paul Gortmaker <paul.gortmaker@windriver.com> wrote:

> Hardware with MCA bus is limited to 386 and 486 class machines
> that are now 20+ years old and typically with less than 32MB
> of memory.  A quick search on the internet, and you see that
> even the MCA hobbyist/enthusiast community has lost interest
> in the early 2000 era and never really even moved ahead from
> the 2.4 kernels to the 2.6 series.
> 
> This deletes anything remaining related to CONFIG_MCA from core
> kernel code and from the x86 architecture.  There is no point in
> carrying this any further into the future.
> 
> One complication to watch for is inadvertently scooping up
> stuff relating to machine check, since there is overlap in
> the TLA name space (e.g. arch/x86/boot/mca.c).

Acked-by: Ingo Molnar <mingo@elte.hu>

Thanks,

	Ingo

  reply	other threads:[~2012-05-17 18:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-17 16:40 [RFC/PATCH 0/5] Delete microchannel [CONFIG_MCA] support Paul Gortmaker
2012-05-17 16:40 ` [PATCH 1/5] arm: remove ability to select CONFIG_MCA Paul Gortmaker
2012-05-17 16:40 ` [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA Paul Gortmaker
2012-05-17 16:51   ` Paul Gortmaker
2012-05-17 21:20     ` Paul Gortmaker
2012-05-17 22:09       ` [RFC PATCH net-next] hp100: delete VG/AnyLAN hp100 Joe Perches
2012-05-17 22:28         ` Francois Romieu
2012-05-17 22:50           ` Joe Perches
2012-05-18 19:28             ` Francois Romieu
2012-05-19 19:28           ` Joel Soete
2012-06-12 12:36         ` Pavel Machek
2012-05-17 22:23       ` [PATCH 2/5] drivers/net: delete all code/drivers depending on CONFIG_MCA David Miller
2012-05-17 16:40 ` [PATCH 3/5] serial: delete the MCA specific 8250 support Paul Gortmaker
2012-05-17 16:46   ` Greg Kroah-Hartman
2012-05-17 16:59     ` Paul Gortmaker
2012-05-17 20:16       ` David Miller
2012-05-17 21:02         ` Paul Gortmaker
2012-05-17 16:40 ` [PATCH 4/5] scsi: delete the MCA specific drivers and driver code Paul Gortmaker
2012-05-17 16:40 ` [PATCH 5/5] MCA: delete all remaining traces of microchannel bus support Paul Gortmaker
2012-05-17 18:00   ` Ingo Molnar [this message]
2012-05-17 22:18   ` H. Peter Anvin
2012-05-17 16:53 ` [RFC/PATCH 0/5] Delete microchannel [CONFIG_MCA] support Linus Torvalds
2012-05-17 17:22   ` Alan Cox
2012-05-17 17:24 ` James Bottomley

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=20120517180001.GA17846@gmail.com \
    --to=mingo@kernel.org \
    --cc=JBottomley@parallels.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=paul.gortmaker@windriver.com \
    --cc=tglx@linutronix.de \
    --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