From: Dave Jones <davej@redhat.com>
To: Vince Weaver <vincent.weaver@maine.edu>
Cc: trinity@vger.kernel.org
Subject: Re: exporting pmu data from perf_event_open.c
Date: Wed, 14 May 2014 11:43:26 -0400 [thread overview]
Message-ID: <20140514154326.GA16439@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1405131441100.24957@vincent-weaver-1.umelst.maine.edu>
On Tue, May 13, 2014 at 02:51:35PM -0400, Vince Weaver wrote:
> I just finished syncing perf_fuzzer against the Trinity 1.4 codebase.
>
> It was a bit of a pain, but I guess still worth doing in order to
> keep perf_event_open.c shared.
>
> I was wondering if you'd consider a patch like the following.
> It exports the perf_event_open() pmus structure, that way perf_fuzzer can
> pretty-print the pmu names. It would save a lot of code duplication.
Sure, if it saves you work why not..
applied, with a munged changelog to change tenses :)
Dave
prev parent reply other threads:[~2014-05-14 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 18:51 exporting pmu data from perf_event_open.c Vince Weaver
2014-05-14 15:43 ` Dave Jones [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=20140514154326.GA16439@redhat.com \
--to=davej@redhat.com \
--cc=trinity@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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).