All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: Dave Jones <davej@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>,
	levon@movementarian.org, phil.el@wanadoo.fr,
	Andrew Morton <akpm@osdl.org>
Subject: Re: Is OPROFILE actively maintained?
Date: Sun, 21 May 2006 13:56:44 -0700	[thread overview]
Message-ID: <20060521205644.GA3420@taniwha.stupidest.org> (raw)
In-Reply-To: <20060521204947.GM8250@redhat.com>

On Sun, May 21, 2006 at 04:49:47PM -0400, Dave Jones wrote:

> Part of the problem with EXPERIMENTAL is that it's been taken
> to mean all sorts of things over the years

yes

> from "this isn't quite ready, but works"

ok for -mm perhaps, not mainline

> to "if you enable this, you're a lunatic".

suitable for neither -mm not mainline

> It's meant that pretty much everyone has to enable
> CONFIG_EXPERIMENTAL anyway for a kernel offering the features
> everyone has come to expect.  As means of example, I'll bet there's
> no (or at least very few) distros that ship a kernel with
> CONFIG_EXPERIMENTAL disabled.

i don't see why we can't audit EXPERIMENTAL users and try to clarify
which ones are really needed over time though

  reply	other threads:[~2006-05-21 20:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-20  2:53 [PATCH] i386 Don't conside oprofile EXPERIMENTAL anymore Chris Wedgwood
2006-05-21 19:49 ` Is OPROFILE actively maintained? Chris Wedgwood
2006-05-21 19:57   ` Dave Jones
2006-05-21 20:17     ` Chris Wedgwood
2006-05-21 20:49       ` Dave Jones
2006-05-21 20:56         ` Chris Wedgwood [this message]
2006-05-21 20:25     ` John Levon
2006-05-22 11:51   ` Alan Cox
2006-05-22 15:15     ` John Levon
2006-05-22 17:50       ` Måns Rullgård
2006-05-22 18:13         ` Chris Wedgwood
2006-05-22 15:27     ` Chris Wedgwood

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=20060521205644.GA3420@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --cc=akpm@osdl.org \
    --cc=davej@redhat.com \
    --cc=levon@movementarian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phil.el@wanadoo.fr \
    --cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.