From: Michael Opdenacker <michael.opdenacker@bootlin.com>
To: "Bezem, Johan (extern)" <JBezem.extern@arri.de>
Cc: docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH] variables.rst: SDKPATHINSTALL correct installation default path
Date: Thu, 29 Feb 2024 12:20:05 +0100 [thread overview]
Message-ID: <54df2516-b2c6-46ca-946c-dafb6e120153@bootlin.com> (raw)
In-Reply-To: <20240226161506.48020-1-jbezem.extern@arri.de>
Hi Johan
On 2/26/24 at 17:15, Bezem, Johan (extern) wrote:
> From: "Bezem, Johan" <jbezem.extern@arri.de>
>
> The SDKPATH variable seems mistakenly identified as the
> default path where the SDK will be installed by the generated
> installation script, unless option '-d' or a manual input
> overrides this default.
>
> The intended variable is SDKPATHINSTALL. SDKPATH indicates
> where the SDK is being composed and built.
>
> The definitions have been added/updated.
>
> Signed-off-by: Johan Bezem <jbezem.extern@arri.de>
> ---
> documentation/overview-manual/concepts.rst | 2 +-
> documentation/ref-manual/variables.rst | 6 +++++-
> 2 files changed, 6 insertions(+), 2 deletions(-)
Thanks for the new version!
Reviewed-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Merged into master-next.
Cheers
Michael.
--
Michael Opdenacker, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2024-02-29 11:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 16:15 [PATCH] variables.rst: SDKPATHINSTALL correct installation default path Johan Bezem
2024-02-29 11:20 ` Michael Opdenacker [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-02-28 13:04 [docs] " Bezem, Johan (extern)
2024-02-23 10:59 Bezem, Johan (extern)
2024-02-13 12:52 Johan Bezem
2024-02-14 9:31 ` [docs] " Michael Opdenacker
2024-02-23 10:19 ` 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=54df2516-b2c6-46ca-946c-dafb6e120153@bootlin.com \
--to=michael.opdenacker@bootlin.com \
--cc=JBezem.extern@arri.de \
--cc=docs@lists.yoctoproject.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).