public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Du, Changbin" <changbin.du@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: changbin.du@intel.com, peterz@infradead.org, mingo@redhat.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf lock: subcommands should include common options
Date: Fri, 17 Mar 2017 23:09:59 +0800	[thread overview]
Message-ID: <20170317150959.GA26124@intel.com> (raw)
In-Reply-To: <20170317140834.GC12825@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1968 bytes --]

On Fri, Mar 17, 2017 at 11:08:34AM -0300, Arnaldo Carvalho de Melo wrote:
> Em Fri, Mar 17, 2017 at 01:53:42PM +0800, changbin.du@intel.com escreveu:
> > From: Changbin Du <changbin.du@intel.com>
> > 
> > When I use -i option for report subcommand, it doesn't accept it.
> > We need add common options using OPT_PARENT macro.
> > 
> > perf lock report -i lock_perf.data
> >   Error: unknown switch `i'
> > 
> >   Usage: perf lock report [<options>]
> > 
> >     -f, --force           don't complain, do it
> >     -k, --key <acquired>  key for sorting ...
> > 
> > Signed-off-by: Changbin Du <changbin.du@intel.com>
> > ---
> >  tools/perf/builtin-lock.c | 19 +++++++++++--------
> >  1 file changed, 11 insertions(+), 8 deletions(-)
> > 
> > diff --git a/tools/perf/builtin-lock.c b/tools/perf/builtin-lock.c
> > index ce3bfb4..710c551 100644
> > --- a/tools/perf/builtin-lock.c
> > +++ b/tools/perf/builtin-lock.c
> > @@ -947,27 +947,30 @@ static int __cmd_record(int argc, const char **argv)
> >  
> >  int cmd_lock(int argc, const char **argv, const char *prefix __maybe_unused)
> >  {
> > +	const struct option lock_options[] = {
> > +	OPT_STRING('i', "input", &input_name, "file", "input file name"),
> > +	OPT_INCR('v', "verbose", &verbose, "be more verbose (show symbol address, etc)"),
> > +	OPT_BOOLEAN('D', "dump-raw-trace", &dump_trace, "dump raw trace in ASCII"),
> > +	OPT_END()
> > +	};
> > +
> >  	const struct option info_options[] = {
> >  	OPT_BOOLEAN('t', "threads", &info_threads,
> >  		    "dump thread list in perf.data"),
> >  	OPT_BOOLEAN('m', "map", &info_map,
> >  		    "map of lock instances (address:name table)"),
> >  	OPT_BOOLEAN('f', "force", &force, "don't complain, do it"),
> 
> Good catch, OPT_PARENT came after 'perf lock', but you forgot 'f', I'm
> adding it and renaming 'lock_options' to 'lock_input_options', ok?
>
I am okay, just go ahead. thanks.

-- 
Thanks,
Changbin Du

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2017-03-17 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-17  5:53 [PATCH] perf lock: subcommands should include common options changbin.du
2017-03-17 14:08 ` Arnaldo Carvalho de Melo
2017-03-17 15:09   ` Du, Changbin [this message]
2017-03-21  6:49 ` [tip:perf/core] perf lock: Subcommands " tip-bot for Changbin Du

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=20170317150959.GA26124@intel.com \
    --to=changbin.du@intel.com \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    /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