public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Andi Kleen <ak@suse.de>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, fastboot@osdl.org
Subject: Re: [PATCH] x86_64 kexec: Remove experimental mark of kexec
Date: Wed, 06 Sep 2006 14:15:15 -0600	[thread overview]
Message-ID: <m1pse8vjjg.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <200609062122.14971.ak@suse.de> (Andi Kleen's message of "Wed, 6 Sep 2006 21:22:14 +0200")

Andi Kleen <ak@suse.de> writes:

> On Wednesday 06 September 2006 18:55, Eric W. Biederman wrote:
>> 
>> kexec has been marked experimental for a year now and all
>> of the serious problems have been worked through.  So it
>> is time (if not past time) to remove the experimental mark.
>> 
>
> Hmm, I personally have some doubts it is really not experimental
> (not because of the kexec code itself, but because of all the other drivers
> that still break)

That is a reasonable viewpoint.  Although by that a lot more of the kernel
deserves to be marked experimental. 

On the perverse side of the sentiment taking off experimental may increase
our number of testers and get the bugs fixed faster :)

> But applied for now.

Thanks.

Eric

  reply	other threads:[~2006-09-06 20:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-06 16:42 [PATCH] x86_64 kexec: Remove experimental mark of kexec Eric W. Biederman
2006-09-06 16:55 ` Eric W. Biederman
2006-09-06 19:22   ` Andi Kleen
2006-09-06 20:15     ` Eric W. Biederman [this message]
2006-09-07  6:20       ` Piet Delaney
2006-09-07  6:55         ` Eric W. Biederman
2006-09-08  1:54           ` Piet Delaney
2006-09-07  5:47     ` Piet Delaney
2006-09-07  6:03       ` Eric W. Biederman

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=m1pse8vjjg.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=fastboot@osdl.org \
    --cc=linux-kernel@vger.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