From: Fabio Estevam <festevam@gmail.com>
To: sbabic@denx.de
Cc: uboot-imx@nxp.com, u-boot@lists.denx.de,
Fabio Estevam <festevam@denx.de>
Subject: [PATCH 3/3] imx: hab: Explain that ivt_offset is optional
Date: Wed, 6 Sep 2023 22:47:27 -0300 [thread overview]
Message-ID: <20230907014727.371324-3-festevam@gmail.com> (raw)
In-Reply-To: <20230907014727.371324-1-festevam@gmail.com>
From: Fabio Estevam <festevam@denx.de>
The ivt_offset parameter is optional for both hab_auth_img_or_fail
and hab_auth_img commands.
Document it in their usage texts to make it clearer.
Signed-off-by: Fabio Estevam <festevam@denx.de>
---
arch/arm/mach-imx/hab.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-imx/hab.c b/arch/arm/mach-imx/hab.c
index ea9c5d3c9fd4..41121d575734 100644
--- a/arch/arm/mach-imx/hab.c
+++ b/arch/arm/mach-imx/hab.c
@@ -700,7 +700,7 @@ U_BOOT_CMD(
"addr length ivt_offset\n"
"addr - image hex address\n"
"length - image hex length\n"
- "ivt_offset - hex offset of IVT in the image"
+ "ivt_offset - hex offset of IVT in the image (optional)"
);
U_BOOT_CMD(
@@ -716,7 +716,7 @@ U_BOOT_CMD(
"addr length ivt_offset\n"
"addr - image hex address\n"
"length - image hex length\n"
- "ivt_offset - hex offset of IVT in the image"
+ "ivt_offset - hex offset of IVT in the image (optional)"
);
U_BOOT_CMD(
--
2.34.1
next prev parent reply other threads:[~2023-09-07 1:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 1:47 [PATCH 1/3] imx: hab: Allow hab_auth_img_or_fail to be called without ivt_offset Fabio Estevam
2023-09-07 1:47 ` [PATCH 2/3] imx: hab: Improve the hab_auth_img_or_fail usage text Fabio Estevam
2023-09-23 18:51 ` sbabic
2023-09-07 1:47 ` Fabio Estevam [this message]
2023-09-23 18:52 ` [PATCH 3/3] imx: hab: Explain that ivt_offset is optional sbabic
2023-09-23 18:51 ` [PATCH 1/3] imx: hab: Allow hab_auth_img_or_fail to be called without ivt_offset sbabic
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=20230907014727.371324-3-festevam@gmail.com \
--to=festevam@gmail.com \
--cc=festevam@denx.de \
--cc=sbabic@denx.de \
--cc=u-boot@lists.denx.de \
--cc=uboot-imx@nxp.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