From: Namhyung Kim <namhyung@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Arnaldo Carvalho de Melo <acme@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH] perf: Build install-man target when installing
Date: Mon, 22 Oct 2012 16:25:24 +0900 [thread overview]
Message-ID: <87mwzfj7dn.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <20121020111625.GB17563@liondog.tnic> (Borislav Petkov's message of "Sat, 20 Oct 2012 13:16:25 +0200")
Hi,
On Sat, 20 Oct 2012 13:16:25 +0200, Borislav Petkov wrote:
> On Fri, Sep 28, 2012 at 07:47:07PM +0200, Borislav Petkov wrote:
>> From: Borislav Petkov <borislav.petkov@amd.com>
>>
>> There's a portion in the "perf list" output refering to the exact
>> specification of raw hardware events. Since this description is in
>> the perf-list manpage, make install-man be built unconditionally when
>> installing perf tool and change the reference in the "perf list" output
>> accordingly.
>>
>> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>
>> ---
>> tools/perf/Makefile | 2 +-
>> tools/perf/util/parse-events.c | 2 +-
>> 2 files changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/tools/perf/Makefile b/tools/perf/Makefile
>> index 251dcd7fb5ac..e77741e22cfb 100644
>> --- a/tools/perf/Makefile
>> +++ b/tools/perf/Makefile
>> @@ -1027,7 +1027,7 @@ perfexec_instdir = $(prefix)/$(perfexecdir)
>> endif
>> perfexec_instdir_SQ = $(subst ','\'',$(perfexec_instdir))
>>
>> -install: all
>> +install: all install-man
It will add additional dependencies of asciidoc, docbook-xsl and/or
something to default perf install command. I don't know it matters
much, but just wanted to say. What if a user want to install the perf
but the required packages for documents are not installed?
>> $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(bindir_SQ)'
>> $(INSTALL) $(OUTPUT)perf '$(DESTDIR_SQ)$(bindir_SQ)'
>> $(INSTALL) -d -m 755 '$(DESTDIR_SQ)$(perfexec_instdir_SQ)/scripts/perl/Perf-Trace-Util/lib/Perf/Trace'
>> diff --git a/tools/perf/util/parse-events.c b/tools/perf/util/parse-events.c
>> index bf5d033ee1b4..f84ac3984708 100644
>> --- a/tools/perf/util/parse-events.c
>> +++ b/tools/perf/util/parse-events.c
>> @@ -1092,7 +1092,7 @@ void print_events(const char *event_glob, bool name_only)
>> printf(" %-50s [%s]\n",
>> "cpu/t1=v1[,t2=v2,t3 ...]/modifier",
>> event_type_descriptors[PERF_TYPE_RAW]);
>> - printf(" (see 'perf list --help' on how to encode it)\n");
>> + printf(" (see 'man perf-list' on how to encode it)\n");
Is this needed? Shouldn't we fix perf --help handling? Please see my
other post on the issue.
Thanks,
Namhyung
>> printf("\n");
>>
>> printf(" %-50s [%s]\n",
>> --
>> 1.7.11.rc1
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2012-10-22 7:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-25 15:52 specifying raw perf events Borislav Petkov
2012-09-25 17:02 ` Arnaldo Carvalho de Melo
2012-09-25 17:03 ` Arnaldo Carvalho de Melo
2012-09-25 17:11 ` Borislav Petkov
2012-09-25 17:45 ` Arnaldo Carvalho de Melo
2012-09-25 17:46 ` Borislav Petkov
2012-09-28 17:47 ` [PATCH] perf: Build install-man target when installing Borislav Petkov
2012-10-20 11:16 ` Borislav Petkov
2012-10-20 15:37 ` Arnaldo Carvalho de Melo
2012-10-22 7:25 ` Namhyung Kim [this message]
2012-10-22 10:07 ` Borislav Petkov
2012-10-22 14:03 ` Arnaldo Carvalho de Melo
2012-10-22 23:13 ` Borislav Petkov
2012-10-23 13:39 ` Arnaldo Carvalho de Melo
2012-10-24 17:03 ` Arnaldo Carvalho de Melo
2012-10-24 17:20 ` Arnaldo Carvalho de Melo
2012-10-24 19:30 ` Borislav Petkov
2012-10-24 19:41 ` Arnaldo Carvalho de Melo
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=87mwzfj7dn.fsf@sejong.aot.lge.com \
--to=namhyung@kernel.org \
--cc=acme@infradead.org \
--cc=borislav.petkov@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).