From: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Richter <tmricht@linux.ibm.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
borntraeger@de.ibm.com, gor@linux.ibm.com,
sumanthk@linux.ibm.com, heiko.carstens@de.ibm.com
Subject: Re: [PATCH] perf test: Test case 66 broken on s390 (lib/traceevent issue)
Date: Thu, 30 Jan 2020 11:58:04 +0100 [thread overview]
Message-ID: <20200130105804.GD3841@kernel.org> (raw)
In-Reply-To: <20200127105553.3cd92ef8@gandalf.local.home>
Em Mon, Jan 27, 2020 at 10:55:53AM -0500, Steven Rostedt escreveu:
> On Mon, 27 Jan 2020 08:34:23 +0100
> Thomas Richter <tmricht@linux.ibm.com> wrote:
>
> > Steven and Masami,
> >
> > thanks for the patch, it fixes this issue!
>
> Thanks for letting me know. I'll add a:
>
> Tested-by: Thomas Richter <tmricht@linux.ibm.com>
>
> to the commit.
So you're taking it, right?
- Arnaldo
> >
> > PS: I should have sent this description earlier, would have saved a week of debugging
> > on my side....
>
> Heh, I do things like this ofter after triggering bugs in others
> code, and will spend a few days debugging it, then finding out that
> there's already a fix to the bug I find (or presenting the problem
> gives a proper fix). I just calk it up as a learning experience ;-)
>
> -- Steve
--
- Arnaldo
next prev parent reply other threads:[~2020-01-30 10:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 7:39 [PATCH] perf test: Test case 66 broken on s390 (lib/traceevent issue) Thomas Richter
2020-01-24 15:07 ` Steven Rostedt
2020-01-24 16:31 ` Masami Hiramatsu
2020-01-24 16:36 ` Steven Rostedt
2020-01-27 7:34 ` Thomas Richter
2020-01-27 15:55 ` Steven Rostedt
2020-01-30 10:58 ` Arnaldo Carvalho de Melo [this message]
2020-01-30 12:54 ` Steven Rostedt
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=20200130105804.GD3841@kernel.org \
--to=arnaldo.melo@gmail.com \
--cc=borntraeger@de.ibm.com \
--cc=gor@linux.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sumanthk@linux.ibm.com \
--cc=tmricht@linux.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.