public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] profile-manual: document how to build perf manpages on target
Date: Mon, 2 Aug 2021 15:05:25 +0200	[thread overview]
Message-ID: <f0d355f9-c994-d202-9fa2-b86ffb9bf75b@bootlin.com> (raw)
In-Reply-To: <20210802093816.vndv4fa25mbypjca@fedora>

Hi Quentin,

Many thanks for the review!

On 8/2/21 11:38 AM, Quentin Schulz wrote:
> Hi Michael,
>
> On Fri, Jul 30, 2021 at 06:06:17PM +0200, Michael Opdenacker wrote:
>> Thanks to closing yocto bug #3388, there is now a simple way
>> to build the perf manpages for use on the target
>>
>> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
>> ---
>>  documentation/profile-manual/usage.rst | 11 ++++++-----
>>  1 file changed, 6 insertions(+), 5 deletions(-)
>>
>> diff --git a/documentation/profile-manual/usage.rst b/documentation/profile-manual/usage.rst
>> index 825290c3f8..ae4efa7f4c 100644
>> --- a/documentation/profile-manual/usage.rst
>> +++ b/documentation/profile-manual/usage.rst
>> @@ -1157,13 +1157,14 @@ section can be found here:
>>  Normally, you should be able to invoke the man pages via perf itself
>>  e.g. 'perf help' or 'perf help record'.
>>  
>> -However, by default Yocto doesn't install man pages, but perf invokes
>> -the man pages for most help functionality. This is a bug and is being
>> -addressed by a Yocto bug: :yocto_bugs:`Bug 3388 - perf: enable man pages for
>> -basic 'help' functionality </show_bug.cgi?id=3388>`.
>> +To have the perf manpages installed on your target, modify your
> s/perf/``perf``/ ?


While I tend to agree here, I believe this change should be made in
another commit. You have many other instances of the "perf" word in this
chapter, like instances of "ftrace" and other tool names.

Let me first propose a coding style for documentation, and once we agree
on one, we'll be able to roll it out progressively on the various documents.

Cheers,

Michael.

-- 
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


      parent reply	other threads:[~2021-08-02 13:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-30 16:06 [PATCH] profile-manual: document how to build perf manpages on target Michael Opdenacker
2021-08-02  9:38 ` [docs] " Quentin Schulz
2021-08-02 12:43   ` Richard Purdie
2021-08-02 13:13     ` Michael Opdenacker
     [not found]     ` <16977F8E4C0D2875.17923@lists.yoctoproject.org>
2021-08-02 16:23       ` Michael Opdenacker
2021-08-02 13:05   ` Michael Opdenacker [this message]

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=f0d355f9-c994-d202-9fa2-b86ffb9bf75b@bootlin.com \
    --to=michael.opdenacker@bootlin.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=quentin.schulz@theobroma-systems.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