From: Jiri Olsa <jolsa@redhat.com>
To: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf: fix perf test case 14 result reporting
Date: Sun, 4 Jun 2017 20:51:19 +0200 [thread overview]
Message-ID: <20170604185057.GA18648@krava> (raw)
In-Reply-To: <c06b8134-4636-c14f-c580-8b45e5256093@linux.vnet.ibm.com>
On Fri, Jun 02, 2017 at 11:58:46AM +0200, Thomas-Mich Richter wrote:
SNBIP
> > I started fixing it some time ago, but got distracted, if you are
> > interested, you're welcome to pick up from my branch ;-)
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> > perf/attr_test
> >
> > thanks,
> > jirka
> >
>
> I have started work on perf tool very recently to get s390 support
> working and up to date.
>
> I downloaded your branch and discovered you have already fixed
> another issue I run into this week. For example
> commit 070b9644981e ("perf tests attr: Do not store failed events")
>
> I can certainly help you to get this test case operational again.
> Maybe you need to pull some of your patches out of your backlog
> and submit them the kernel to get to a common base to work on.
>
> I suggest we should move the discussion to the linux-perf-users
> mailing list.
>
> Your thoughts?
good idea, for me it'd be best if you pull them and change them
as you see fit.. I dont think I'll get to it any time soon
thanks,
jirka
prev parent reply other threads:[~2017-06-04 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 12:34 [PATCH] perf: fix perf test case 14 result reporting Thomas Richter
2017-06-01 13:20 ` Arnaldo Carvalho de Melo
2017-06-01 21:04 ` Jiri Olsa
2017-06-02 9:58 ` Thomas-Mich Richter
2017-06-02 14:09 ` Arnaldo Carvalho de Melo
2017-06-02 14:11 ` Arnaldo Carvalho de Melo
2017-06-04 18:51 ` Jiri Olsa
2017-06-06 5:02 ` Thomas-Mich Richter
2017-06-04 18:51 ` Jiri Olsa [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=20170604185057.GA18648@krava \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=tmricht@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.