From: Michael Petlan <mpetlan@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Thomas-Mich Richter <tmricht@linux.vnet.ibm.com>,
linux-perf-users@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
Namhyung Kim <namhyung@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: Re: [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace
Date: Tue, 12 Dec 2017 17:24:43 +0100 (CET) [thread overview]
Message-ID: <alpine.LRH.2.20.1712121723290.9416@Diego> (raw)
In-Reply-To: <20171212151948.GN3958@kernel.org>
Hey Arnaldo, this one did not remove the s390x hack and also, won't work
on arm. Please use the one I just have sent, few seconds ago...
On Tue, 12 Dec 2017, Arnaldo Carvalho de Melo wrote:
> Em Tue, Dec 12, 2017 at 11:57:07AM -0300, Arnaldo Carvalho de Melo escreveu:
> > So the patch below does the trick for me, can you please check if does
> > for you?
>
> So I've put this with a long explanation at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git/commit/?h=tmp.perf/core&id=ba15be2acc9e35dc9f034fef3aa292406b518b04
>
> - Arnaldo
>
next prev parent reply other threads:[~2017-12-12 16:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LRH.2.20.1712081845230.9416@Diego>
2017-12-11 15:43 ` [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace Arnaldo de Melo
2017-12-11 17:07 ` Arnaldo Carvalho de Melo
2017-12-12 3:05 ` Michael Petlan
2017-12-12 14:57 ` Arnaldo Carvalho de Melo
2017-12-12 15:19 ` Arnaldo Carvalho de Melo
2017-12-12 16:24 ` Michael Petlan [this message]
2017-12-12 17:12 ` Arnaldo Carvalho de Melo
2017-12-14 12:08 ` Thomas-Mich Richter
2017-12-14 14:03 ` Arnaldo Carvalho de Melo
2017-12-28 15:33 ` [tip:perf/core] perf test shell: Fix check open filename arg using 'perf trace' tip-bot for Michael Petlan
2017-12-12 16:30 ` [PATCH v2] perf test shell: Fix check open filename arg using 'perf trace Michael Petlan
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=alpine.LRH.2.20.1712121723290.9416@Diego \
--to=mpetlan@redhat.com \
--cc=acme@kernel.org \
--cc=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=namhyung@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 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).