From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
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 18:23:15 +0200 [thread overview]
Message-ID: <55a6e8aa-a959-8bce-abc5-7be14ebb70da@bootlin.com> (raw)
In-Reply-To: <16977F8E4C0D2875.17923@lists.yoctoproject.org>
On 8/2/21 3:13 PM, Michael Opdenacker wrote:
> Hi Richard,
>
> Thank you for the review!
>
> On 8/2/21 2:43 PM, Richard Purdie wrote:
>> On Mon, 2021-08-02 at 11:38 +0200, Quentin Schulz wrote:\
>>> Should perf-doc not be the only package added to IMAGE_INSTALL? I assume
>>> one wants perf-doc only if they need perf so they would already have it
>>> in their image?
>>>
>>> s/perf // is what I suggest here.
>> Personally, I think it is better to be specific. I did end up just installing
>> the doc package when I first attempted to test this and if I can do that... :/.
> LOL! We promise we will continue to improve the documentation to make
> your user life easier!
>
> Thanks again,
> Michael
I merged this change in master-next. Thanks again for your reviews!
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-08-02 16:23 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 [this message]
2021-08-02 13:05 ` Michael Opdenacker
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=55a6e8aa-a959-8bce-abc5-7be14ebb70da@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=richard.purdie@linuxfoundation.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