From: "Michael Opdenacker" <michael.opdenacker@bootlin.com>
To: Jon Mason <jdmason@kudzu.us>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 3/3] docs: update docs with new tune locations
Date: Wed, 11 Aug 2021 12:07:40 +0200 [thread overview]
Message-ID: <6a5a636f-c049-5385-9f6e-0f88300970d7@bootlin.com> (raw)
In-Reply-To: <20210810214503.17791-4-jdmason@kudzu.us>
Hi Jon,
On 8/10/21 11:45 PM, Jon Mason wrote:
> Signed-off-by: Jon Mason <jdmason@kudzu.us>
> ---
> documentation/bsp-guide/bsp.rst | 4 ++--
> documentation/ref-manual/variables.rst | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/documentation/bsp-guide/bsp.rst b/documentation/bsp-guide/bsp.rst
> index 5f62376d69e8..956d90db1aaa 100644
> --- a/documentation/bsp-guide/bsp.rst
> +++ b/documentation/bsp-guide/bsp.rst
> @@ -1266,7 +1266,7 @@ located in the layer ``poky/meta-yocto-bsp/conf/machine`` and is named
> EXTRA_IMAGEDEPENDS += "u-boot"
>
> DEFAULTTUNE ?= "cortexa8hf-neon"
> - include conf/machine/include/tune-cortexa8.inc
> + include conf/machine/include/arm/tune-cortexa8.inc
>
> IMAGE_FSTYPES += "tar.bz2 jffs2 wic wic.bmap"
> EXTRA_IMAGECMD_jffs2 = "-lnp "
> @@ -1344,7 +1344,7 @@ Project Reference Manual.
> .. note::
>
> The include statement that pulls in the
> - ``conf/machine/include/tune-cortexa8.inc`` file provides many tuning
> + ``conf/machine/include/arm/tune-cortexa8.inc`` file provides many tuning
> possibilities.
>
> - :term:`IMAGE_FSTYPES`: The
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 115094013313..1c4897bf65e7 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -8245,7 +8245,7 @@ system and gives an overview of their function and contents.
>
> These tune-specific package architectures are defined in the machine
> include files. Here is an example of the "core2-32" tuning as used in
> - the ``meta/conf/machine/include/tune-core2.inc`` file::
> + the ``meta/conf/machine/include/x86/tune-core2.inc`` file::
>
> TUNE_PKGARCH_tune-core2-32 = "core2-32"
>
Thanks for the patch!
Indeed, I believe that moving all arm includes to a specific directory
would be more consistent, but that's just from the perspective of
someone looking at the source repositories. I don't know how much
trouble the big change would cause.
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-08-11 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-10 21:45 [PATCH 0/3] tunes: the great migration Jon Mason
2021-08-10 21:45 ` [PATCH 1/3] conf/machine: move tune files to architecture directories Jon Mason
2021-08-10 21:45 ` [PATCH 2/3] yocto-bsp: update machine confs with new tune locations Jon Mason
2021-08-13 8:19 ` [OE-core] " Alexandre Belloni
2021-08-10 21:45 ` [PATCH 3/3] docs: update docs " Jon Mason
2021-08-11 10:07 ` Michael Opdenacker [this message]
[not found] ` <169A389D543FF76C.17558@lists.openembedded.org>
2021-08-13 10:03 ` [OE-core] " Michael Opdenacker
2021-08-13 12:48 ` 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=6a5a636f-c049-5385-9f6e-0f88300970d7@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=jdmason@kudzu.us \
--cc=openembedded-core@lists.openembedded.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