linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@samba.org>
To: Scott Wood <scottwood@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/2] perf_event: Build callchain code regardless of hardware event support.
Date: Fri, 26 Feb 2010 11:09:48 +1100	[thread overview]
Message-ID: <20100226000948.GA7706@brick.ozlabs.ibm.com> (raw)
In-Reply-To: <20100226000433.GA17033@loki.buserror.net>

On Thu, Feb 25, 2010 at 06:04:33PM -0600, Scott Wood wrote:
> It's also useful for software events, as well as future support for
> other types of hardware counters.
> 
> Signed-off-by: Scott Wood <scottwood@freescale.com>

Acked-by: Paul Mackerras <paulus@samba.org>

  reply	other threads:[~2010-02-26  0:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-26  0:04 [PATCH 1/2] perf_event: Build callchain code regardless of hardware event support Scott Wood
2010-02-26  0:09 ` Paul Mackerras [this message]
2010-03-04 16:47   ` Kumar Gala

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=20100226000948.GA7706@brick.ozlabs.ibm.com \
    --to=paulus@samba.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=scottwood@freescale.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;
as well as URLs for NNTP newsgroup(s).