From: Christoph Hellwig <hch@infradead.org>
To: Matt Redfearn <matt.redfearn@mips.com>
Cc: James Hogan <jhogan@kernel.org>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, Huacai Chen <chenhc@lemote.com>,
linux-kernel@vger.kernel.org,
Jiaxun Yang <jiaxun.yang@flygoat.com>,
Krzysztof Kozlowski <krzk@kernel.org>,
Robert Richter <rric@kernel.org>,
oprofile-list@lists.sf.net,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [RFC PATCH] MIPS: Oprofile: Drop support
Date: Tue, 24 Apr 2018 06:59:00 -0700 [thread overview]
Message-ID: <20180424135900.GA11224@infradead.org> (raw)
In-Reply-To: <1524574554-7451-1-git-send-email-matt.redfearn@mips.com>
On Tue, Apr 24, 2018 at 01:55:54PM +0100, Matt Redfearn wrote:
> The core oprofile code in drivers/oprofile/ has not seeen significant
> maintenance other than fixes to changes in other parts of the tree for
> the last 5 years at least. It looks as through the perf tool has
> more or less superceeded it's functionality.
> Additionally the MIPS architecture support has bitrotted to an extent
> meaning it is not currently functional.
I wonder if time has come to drop oprofile support entirely.
(in addition to your patch which seems more urgent)
prev parent reply other threads:[~2018-04-24 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 12:55 Matt Redfearn
2018-04-24 13:05 ` James Hogan
2018-04-24 13:15 ` Matt Redfearn
2018-05-04 9:30 ` Robert Richter
2018-05-04 9:54 ` Matt Redfearn
2018-05-04 10:26 ` Robert Richter
2018-05-04 11:03 ` Matt Redfearn
2018-05-04 12:27 ` Robert Richter
2018-05-04 12:56 ` Ralf Baechle
2018-05-04 12:59 ` Matt Redfearn
2018-04-24 13:59 ` Christoph Hellwig [this message]
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=20180424135900.GA11224@infradead.org \
--to=hch@infradead.org \
--cc=chenhc@lemote.com \
--cc=jhogan@kernel.org \
--cc=jiaxun.yang@flygoat.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=matt.redfearn@mips.com \
--cc=oprofile-list@lists.sf.net \
--cc=ralf@linux-mips.org \
--cc=rric@kernel.org \
--cc=torvalds@linux-foundation.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®