From: Ralf Baechle <ralf@linux-mips.org>
To: Mark E Mason <mark.e.mason@broadcom.com>
Cc: "Shanthi Kiran Pendyala (skiranp)" <skiranp@cisco.com>,
linux-mips <linux-mips@linux-mips.org>
Subject: Re: Oprofile on sibyte 2.4.18 kernel
Date: Wed, 12 Apr 2006 00:24:05 +0200 [thread overview]
Message-ID: <20060411222405.GA14848@linux-mips.org> (raw)
In-Reply-To: <7E000E7F06B05C49BDBB769ADAF44D07989B08@NT-SJCA-0750.brcm.ad.broadcom.com>
On Tue, Apr 11, 2006 at 02:42:06PM -0700, Mark E Mason wrote:
> FYI: don't use the oprofile tools tarball - use the latest from the CVS
> site on sourceforge. The last tarball on the website is more than a bit
> out of date.
That's documented in the wiki btw :-)
Ralf
next prev parent reply other threads:[~2006-04-12 14:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-11 21:42 Oprofile on sibyte 2.4.18 kernel Mark E Mason
2006-04-11 22:24 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 23:29 Mark E Mason
2006-04-11 23:09 Shanthi Kiran Pendyala (skiranp)
2006-04-11 1:55 Shanthi Kiran Pendyala (skiranp)
2006-04-10 17:37 Mark E Mason
2006-04-07 20:38 Shanthi Kiran Pendyala (skiranp)
2006-04-07 23:20 ` Ralf Baechle
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=20060411222405.GA14848@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.e.mason@broadcom.com \
--cc=skiranp@cisco.com \
/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