From: Arnd Bergmann <arnd.bergmann@de.ibm.com>
To: Bob Nelson <rrnelson@linux.vnet.ibm.com>
Cc: eranian@hpl.hp.com, linux kernel <linux-kernel@vger.kernel.org>,
oprofile <oprofile-list@lists.sourceforge.net>
Subject: Re: 2.6.22 new perfmon code base + libpfm + pfmon
Date: Wed, 1 Aug 2007 16:29:03 +0200 [thread overview]
Message-ID: <200708011629.03828.arnd.bergmann@de.ibm.com> (raw)
In-Reply-To: <200708010922.41551.rrnelson@linux.vnet.ibm.com>
On Wednesday 01 August 2007, Bob Nelson wrote:
> It looks to me like you were saying you would remove this extension to the
> OProfile file system (/dev/oprofile/implementation).
> However, it looks like it has made it into the mainline kernel code.
Just to be clear, this problem showed up in my own kernel patch set
from http://www.kernel.org/pub/linux/kernel/people/arnd/patches/2.6.22-arnd1/,
not in mainline.
Arnd <><
next prev parent reply other threads:[~2007-08-01 14:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 14:02 2.6.22 new perfmon code base + libpfm + pfmon Stephane Eranian
2007-08-01 14:22 ` Bob Nelson
2007-08-01 14:29 ` Arnd Bergmann [this message]
2007-08-01 15:09 ` Bob Nelson
2007-08-06 18:09 ` David Rientjes
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=200708011629.03828.arnd.bergmann@de.ibm.com \
--to=arnd.bergmann@de.ibm.com \
--cc=eranian@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=rrnelson@linux.vnet.ibm.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