linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Auld <pauld@redhat.com>
To: Slavomir Kaslev <kaslevs@vmware.com>
Cc: rostedt@goodmis.org, linux-trace-devel@vger.kernel.org,
	ykaradzhov@vmware.com, jbacik@fb.com, tstoyanov@vmware.com,
	slavomir.kaslev@gmail.com
Subject: Re: [PATCH v4 2/2] trace-cmd: Document record --no-filter option in record's man page
Date: Wed, 17 Apr 2019 10:05:14 -0400	[thread overview]
Message-ID: <20190417140514.GE6118@pauld.bos.csb> (raw)
In-Reply-To: <20190417130959.10064-3-kaslevs@vmware.com>

On Wed, Apr 17, 2019 at 04:09:59PM +0300 Slavomir Kaslev wrote:
> Add a section about the new --no-filter argument of `trace-cmd record`
> to its man page.
> 
> Signed-off-by: Slavomir Kaslev <kaslevs@vmware.com>
> ---
>  Documentation/trace-cmd-record.1.txt | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/Documentation/trace-cmd-record.1.txt b/Documentation/trace-cmd-record.1.txt
> index 68afa16..b230aa8 100644
> --- a/Documentation/trace-cmd-record.1.txt
> +++ b/Documentation/trace-cmd-record.1.txt
> @@ -83,6 +83,10 @@ OPTIONS
>  
>      The above are usually safe to use to compare fields.
>  
> +*--no-filter*::
> +    Do not set any event filters, including the default one which ignores events
> +    caused by trace-cmd itself.
> +
>  *-R* 'trigger'::
>      Specify a trigger for the previous event. This must come after a *-e*. 
>      This will add a given trigger to the given event. To only enable the trigger
> -- 
> 2.19.1
> 

Acked-by: Phil Auld <pauld@redhat.com>

and/or

Tested-by: Phil Auld <pauld@redhat.com>




Cheers,
Phil


-- 

  reply	other threads:[~2019-04-17 14:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-17 13:09 [PATCH v4 0/2] Optimize pid filters Slavomir Kaslev
2019-04-17 13:09 ` [PATCH v4 1/2] trace-cmd: Optimize how pid filters are expressed Slavomir Kaslev
2019-04-17 13:58   ` Phil Auld
2019-04-17 14:18     ` John Kacur
2019-04-17 14:25       ` Phil Auld
2019-04-17 14:52         ` Steven Rostedt
2019-04-17 14:52     ` Steven Rostedt
2019-04-17 14:54     ` Steven Rostedt
2019-04-17 13:09 ` [PATCH v4 2/2] trace-cmd: Document record --no-filter option in record's man page Slavomir Kaslev
2019-04-17 14:05   ` Phil Auld [this message]
2019-04-17 16:19   ` Steven Rostedt
2019-04-17 16:24     ` 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=20190417140514.GE6118@pauld.bos.csb \
    --to=pauld@redhat.com \
    --cc=jbacik@fb.com \
    --cc=kaslevs@vmware.com \
    --cc=linux-trace-devel@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=slavomir.kaslev@gmail.com \
    --cc=tstoyanov@vmware.com \
    --cc=ykaradzhov@vmware.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).