From: Tom Rini <trini@kernel.crashing.org>
To: Andy Fleming <afleming@freescale.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH] Remove 604 perfmon from ppc_htab
Date: Tue, 30 Nov 2004 14:04:31 -0700 [thread overview]
Message-ID: <20041130210431.GJ9894@smtp.west.cox.net> (raw)
In-Reply-To: <F9AAB23C-4254-11D9-A096-000393C30512@freescale.com>
On Mon, Nov 29, 2004 at 04:21:11PM -0600, Andy Fleming wrote:
> This patch removes the 604 performance monitor counters from ppc_htab.
> The reason is that people have said that no one uses them, and ppc_htab
> is not the right place for them. Any objections?
Is all of this properly hooked into oprofile(/is perfmon in -Linus now?)
etc now? If so, this sounds like a fine thing to get into 2.6.11.
--
Tom Rini
http://gate.crashing.org/~trini/
prev parent reply other threads:[~2004-11-30 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 22:21 [PATCH] Remove 604 perfmon from ppc_htab Andy Fleming
2004-11-30 21:04 ` Tom Rini [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=20041130210431.GJ9894@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@ozlabs.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;
as well as URLs for NNTP newsgroup(s).