From: "H. Peter Anvin" <hpa@zytor.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
"Ozan Çağlayan" <ozan@pardus.org.tr>,
"Yinghai Lu" <yinghai@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
mingo@elte.hu, a.p.zijlstra@chello.nl, stable@kernel.org,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"Jaswinder Singh Rajput" <jaswinder@kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: RFC: deprecate CONFIG_X86_CPU_DEBUG and schedule it for rapid removal
Date: Fri, 22 Jan 2010 17:05:08 -0800 [thread overview]
Message-ID: <4B5A4B44.3010002@zytor.com> (raw)
In-Reply-To: <20100122165356.55cf88aa.akpm@linux-foundation.org>
On 01/22/2010 04:53 PM, Andrew Morton wrote:
>
> Would it not be better to fix that problem (perhaps just with the
> revert) so that 2.6.33, 2.6.32.x and earlier can be fixed? Then we can
> nuke the feature in 2.6.34.
>
> Alternatively, we can nuke the feature from 2.6.33 and 2.6.32.x and
> earlier right now. Where "nuke" might mean "make it difficult to
> enable".
>
> Whatever. Bottom line is that it'd be nice to do something to fix up
> 2.6.33 and earlier.
>
I would be all for nuking the feature immediately. The easiest way to
nuke the feature quickly is to make it a noninteractive Kconfig feature.
All in favor?
-hpa
next prev parent reply other threads:[~2010-01-23 1:06 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 18:51 Boot hangs after "Freeing initrd memory" with 2.6.31.11 Ozan Çağlayan
2010-01-14 6:58 ` Ozan Çağlayan
2010-01-14 7:43 ` Yinghai Lu
2010-01-14 7:48 ` Ozan Çağlayan
2010-01-14 10:35 ` Ozan Çağlayan
2010-01-14 13:08 ` Ozan Çağlayan
2010-01-14 13:36 ` Ozan Çağlayan
2010-01-16 12:28 ` Ozan Çağlayan
2010-01-16 22:12 ` Rafael J. Wysocki
2010-01-17 8:43 ` Ozan Çağlayan
2010-01-17 13:43 ` Rafael J. Wysocki
2010-01-17 9:22 ` Ozan Çağlayan
2010-01-17 13:44 ` Rafael J. Wysocki
2010-01-18 1:26 ` RFC: deprecate CONFIG_X86_CPU_DEBUG and schedule it for rapid removal H. Peter Anvin
2010-01-18 21:28 ` Rafael J. Wysocki
2010-01-23 0:53 ` Andrew Morton
2010-01-23 1:05 ` H. Peter Anvin [this message]
2010-01-23 1:20 ` [stable] " Greg KH
2010-01-23 1:51 ` H. Peter Anvin
2010-01-23 1:59 ` Linus Torvalds
2010-01-23 5:22 ` Ingo Molnar
2010-01-18 0:58 ` Boot hangs after "Freeing initrd memory" with 2.6.31.11 H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2010-01-23 2:34 RFC: deprecate CONFIG_X86_CPU_DEBUG and schedule it for rapid removal 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=4B5A4B44.3010002@zytor.com \
--to=hpa@zytor.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=jaswinder@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ozan@pardus.org.tr \
--cc=rjw@sisk.pl \
--cc=stable@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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