public inbox for docs@lists.yoctoproject.org
 help / color / mirror / Atom feed
From: "Ulrich Ölmann" <u.oelmann@pengutronix.de>
To: michael.opdenacker@bootlin.com
Cc: Bruce Ashfield <bruce.ashfield@gmail.com>,
	"Michael Opdenacker via lists.yoctoproject.org"
	<michael.opdenacker=bootlin.com@lists.yoctoproject.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] ref-manual: document KERNEL_LOCALVERSION
Date: Thu, 02 Nov 2023 10:55:23 +0100	[thread overview]
Message-ID: <6rjzr0tr2h.fsf@pengutronix.de> (raw)
In-Reply-To: <20231027092935.1601588-1-michael.opdenacker@bootlin.com>

Hi Michael,

just a small typo, otherwise a good description.

On Fri, Oct 27 2023 at 11:29 +0200, "Michael Opdenacker via lists.yoctoproject.org" <michael.opdenacker=bootlin.com@lists.yoctoproject.org> wrote:
> From: Michael Opdenacker <michael.opdenacker@bootlin.com>
>
> Introduced by
> https://git.yoctoproject.org/poky/commit/?id=66ed174ccdf7a89cb998f503cc6b631e2d1adcc0
>
> Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
> CC: Bruce Ashfield <bruce.ashfield@gmail.com>
> ---
>  documentation/ref-manual/variables.rst | 10 ++++++++++
>  1 file changed, 10 insertions(+)
>
> diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
> index 03234d3f78..771eb91af6 100644
> --- a/documentation/ref-manual/variables.rst
> +++ b/documentation/ref-manual/variables.rst
> @@ -2485,6 +2485,16 @@ system and gives an overview of their function and contents.
>        external tools. See the :ref:`ref-classes-kernel-yocto` class in
>        ``meta/classes-recipe`` to see how the variable is used.
>  
> +   :term:`KERNEL_LOCALVERSION`
> +      This variable allows to appends a string to the version

s/appends/append/

Thanks and best regards
Ulrich


> +      of the kernel image. This corresponds to the ``CONFIG_LOCALVERSION``
> +      kernel configuration parameter.
> +
> +      Using this variable is only useful when you are using a kernel recipe
> +      inheriting the :ref:`ref-classes-kernel` class, and which doesn't
> +      already set a local version. Therefore, setting this variable has no
> +      impact on ``linux-yocto`` kernels.
> +
>     :term:`EXTERNAL_TOOLCHAIN`
>        When you intend to use an
>        :ref:`external toolchain <dev-manual/external-toolchain:optionally using an external toolchain>`,
-- 
Pengutronix e.K.                           | Ulrich Ölmann               |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |


  parent reply	other threads:[~2023-11-02  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-27  9:29 [PATCH] ref-manual: document KERNEL_LOCALVERSION michael.opdenacker
2023-10-27 11:27 ` [docs] " Daniel Ammann
2023-10-27 15:09   ` Michael Opdenacker
2023-11-02  9:55 ` Ulrich Ölmann [this message]
2023-11-02 14:52   ` Robert P. J. Day
2023-11-02 15:17     ` Michael Opdenacker
     [not found] ` <1793C5EB6ECDE964.11290@lists.yoctoproject.org>
2023-11-02 10:01   ` Ulrich Ölmann
2023-11-02 13:33     ` 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=6rjzr0tr2h.fsf@pengutronix.de \
    --to=u.oelmann@pengutronix.de \
    --cc=bruce.ashfield@gmail.com \
    --cc=docs@lists.yoctoproject.org \
    --cc=michael.opdenacker=bootlin.com@lists.yoctoproject.org \
    --cc=michael.opdenacker@bootlin.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