public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Tommi Rantala <tt.rantala@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Tommi Rantala <tommi.t.rantala@nokia.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	Hendrik Brueckner <brueckner@linux.ibm.com>,
	Michael Petlan <mpetlan@redhat.com>,
	Kim Phillips <kim.phillips@arm.com>
Subject: Re: [PATCH] perf tests shell: Skip trace+probe_vfs_getname.sh if built without trace support
Date: Fri, 15 Feb 2019 13:43:49 -0300	[thread overview]
Message-ID: <20190215164349.GA31177@kernel.org> (raw)
In-Reply-To: <20190215134253.11454-1-tt.rantala@gmail.com>

Em Fri, Feb 15, 2019 at 03:42:46PM +0200, Tommi Rantala escreveu:
> From: Tommi Rantala <tommi.t.rantala@nokia.com>
> 
> If perf was built without trace support, trace+probe_vfs_getname.sh
> fails:
> 
>   # perf trace -h
>   perf: 'trace' is not a perf-command. See 'perf --help'
> 
>   # perf test 64
>   64: Check open filename arg using perf trace + vfs_getname: FAILED!
> 
> Check trace support, so that we'll skip the test:
> 
>   # perf test 64
>   64: Check open filename arg using perf trace + vfs_getname: Skip

Thanks, applied.

- Arnaldo

  reply	other threads:[~2019-02-15 16:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-15 13:42 [PATCH] perf tests shell: Skip trace+probe_vfs_getname.sh if built without trace support Tommi Rantala
2019-02-15 16:43 ` Arnaldo Carvalho de Melo [this message]
2019-02-28  7:37 ` [tip:perf/core] " tip-bot for Tommi Rantala

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=20190215164349.GA31177@kernel.org \
    --to=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=brueckner@linux.ibm.com \
    --cc=jolsa@redhat.com \
    --cc=kim.phillips@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mpetlan@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tommi.t.rantala@nokia.com \
    --cc=tt.rantala@gmail.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