All of lore.kernel.org
 help / color / mirror / Atom feed
From: Quentin Schulz <foss+buildroot@0leil.net>
To: buildroot@buildroot.org
Cc: Quentin Schulz <foss+buildroot@0leil.net>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	Etienne Carriere <etienne.carriere@linaro.org>
Subject: [Buildroot] [PATCH] boot/optee-os: fix typo in help message of BR2_TARGET_OPTEE_OS_CUSTOM_TARBALL
Date: Mon,  4 Jul 2022 13:27:04 +0200	[thread overview]
Message-ID: <20220704112704.40656-1-foss+buildroot@0leil.net> (raw)

From: Quentin Schulz <quentin.schulz@theobroma-systems.com>

The custom tarball option should be given a URL pointing to an OP-TEE OS
tarball and not a "kernel" one.

Fixes: 9c79b369d69c "boot/optee-os: add support for custom tarball URL"
Cc: Quentin Schulz <foss+buildroot@0leil.net>
Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
---
 boot/optee-os/Config.in | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/boot/optee-os/Config.in b/boot/optee-os/Config.in
index 62e4adcf55..f199de31eb 100644
--- a/boot/optee-os/Config.in
+++ b/boot/optee-os/Config.in
@@ -28,7 +28,7 @@ config BR2_TARGET_OPTEE_OS_LATEST
 config BR2_TARGET_OPTEE_OS_CUSTOM_TARBALL
 	bool "Custom tarball"
 	help
-	  This option allows to specify a URL pointing to a kernel
+	  This option allows to specify a URL pointing to an OP-TEE OS
 	  source tarball. This URL can use any protocol recognized by
 	  Buildroot, like http://, ftp://, file:// or scp://.
 
-- 
2.36.1

_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

             reply	other threads:[~2022-07-04 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-04 11:27 Quentin Schulz [this message]
2022-07-04 15:41 ` [Buildroot] [PATCH] boot/optee-os: fix typo in help message of BR2_TARGET_OPTEE_OS_CUSTOM_TARBALL Yann E. MORIN

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=20220704112704.40656-1-foss+buildroot@0leil.net \
    --to=foss+buildroot@0leil.net \
    --cc=buildroot@buildroot.org \
    --cc=etienne.carriere@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.