From: Gregory Haskins <gregory.haskins@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
"Carlos R. Mafra" <crmafra@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: perf: Problem compiling /tools/perf/Documentation in 2.6.31-rc6
Date: Fri, 21 Aug 2009 07:35:17 -0400 [thread overview]
Message-ID: <4A8E8675.1070100@gmail.com> (raw)
In-Reply-To: <20090821113134.GB24647@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Ingo Molnar wrote:
> * Kyle McMartin <kyle@mcmartin.ca> wrote:
>
>> On Thu, Aug 20, 2009 at 03:00:38PM -0400, Gregory Haskins wrote:
>>> Hi Ingo,
>>>
>>> I'm seeing this in 2.6.31-rc6:
>>>
>>> ghaskins@dev:~/sandbox/git/fabric/linux-2.6/tools/perf/Documentation> make
>>> SUBDIR ../
>>> make[1]: `PERF-VERSION-FILE' is up to date.
>>> ASCIIDOC perf-examples.html
>>> ERROR: perf-examples.txt: line 1: manpage document title is mandatory
>>> FAILED: perf-examples.txt: line 8: illegal style name: From an e-mail by
>>> Ingo Molnar
>>> make: *** [perf-examples.html] Error 1
>>>
>>> It could very well be pilot error. Any ideas?
>>>
>> This was fixed in a recent commit to tip, probably upstream by now.
>> http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commitdiff;h=2932cffc89e9a1476b28a59896fa4f81e0d4f131
>
> Yeah, the fix is upstream now, Linus pulled it two days ago.
>
> Ingo
Thanks all,
-Greg
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 267 bytes --]
next prev parent reply other threads:[~2009-08-21 11:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 19:00 perf: Problem compiling /tools/perf/Documentation in 2.6.31-rc6 Gregory Haskins
2009-08-20 22:15 ` Kyle McMartin
2009-08-21 11:31 ` Ingo Molnar
2009-08-21 11:35 ` Gregory Haskins [this message]
2009-08-20 22:19 ` Carlos R. Mafra
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=4A8E8675.1070100@gmail.com \
--to=gregory.haskins@gmail.com \
--cc=crmafra@gmail.com \
--cc=kyle@mcmartin.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.