From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
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,
"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 18:34:53 -0800 [thread overview]
Message-ID: <fea02893-f940-4e12-9136-2953c7313544@email.android.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
Makes sense. Will do.
"Linus Torvalds" <torvalds@linux-foundation.org> wrote:
>
>
>On Fri, 22 Jan 2010, Andrew Morton wrote:
>>
>> We know that enabling this feature will cause some machines to hang,
>> and that this problem has existed for six months.
>>
>> 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.
>
>Another way of looking at is "we know it's been broken for six months, and
>clearly nobody really ever enabled it in any distro, and even getting a
>bug report on it took forever. So why keep it around at all"?
>
>So I'd personally rather just remove it outright than deprecate it or even
>try to fix it. Since clearly absolutely nobody depends on it.
>
>The usual reason for deprecating a feature is to give people time to move
>away from it, but since clearly nobody uses it...
>
> Linus
--
Sent from my mobile phone, pardon any lack of formatting.
next reply other threads:[~2010-01-23 2:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 2:34 H. Peter Anvin [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-13 18:51 Boot hangs after "Freeing initrd memory" with 2.6.31.11 Ozan Çağlayan
2010-01-16 22:12 ` 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
2010-01-23 1:59 ` Linus Torvalds
2010-01-23 5:22 ` Ingo Molnar
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=fea02893-f940-4e12-9136-2953c7313544@email.android.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
all inboxes | Powered by JetHome®