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:17:20 -0700 [thread overview]
Message-ID: <20060521201720.GA2712@taniwha.stupidest.org> (raw)
In-Reply-To: <20060521195710.GL8250@redhat.com>
On Sun, May 21, 2006 at 03:57:10PM -0400, Dave Jones wrote:
> Why on earth would we want to remove a working feature ?
We don't. I personally don't want to see it go, I use it myself.
> Just because it isn't getting patched every release doesn't mean
> it's rotting, Oprofile is actually one of the few kernel features
> which I don't recall a single regression in since 2.6.0
It works for me, still others have claimed it's unmaintained and has
issues that have not been address.
> BROKEN is for stuff that doesn't compile, or is fundamentally flawed
> beyond repair at the current time (For example, needs infrastructure
> work to happen before it can work correctly).
Sure, based on my personal experience oprofile works fine, I'm just
putting an idea out there given comments from others.
> Oprofile fits neither of those categories.
So it should remain EXPERIMENTAL then in your view?
next prev parent reply other threads:[~2006-05-21 20:17 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 [this message]
2006-05-21 20:49 ` Dave Jones
2006-05-21 20:56 ` Chris Wedgwood
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=20060521201720.GA2712@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 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®