From: "Daniel Wagenknecht" <dwagenknecht@emlix.com>
To: docs@lists.yoctoproject.org
Subject: [PATCH 1/2] ref-manual: variables: fixup example in IMAGE_CMD
Date: Mon, 14 Jun 2021 07:30:12 +0200 [thread overview]
Message-ID: <20210614053013.68669-2-dwagenknecht@emlix.com> (raw)
In-Reply-To: <20210614053013.68669-1-dwagenknecht@emlix.com>
The example for IMAGE_CMD_jffs2 given in the glossary for IMAGE_CMD
didn't align with the implementation anymore. Update it to match the
implementation.
Signed-off-by: Daniel Wagenknecht <dwagenknecht@emlix.com>
---
documentation/ref-manual/variables.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/documentation/ref-manual/variables.rst b/documentation/ref-manual/variables.rst
index ee1043108..1be825fab 100644
--- a/documentation/ref-manual/variables.rst
+++ b/documentation/ref-manual/variables.rst
@@ -2952,8 +2952,8 @@ system and gives an overview of their function and contents.
``btrfs``, and so forth). When setting this variable, you should use
an override for the associated type. Here is an example::
- IMAGE_CMD_jffs2 = "mkfs.jffs2 --root=${IMAGE_ROOTFS} \
- --faketime --output=${IMGDEPLOYDIR}/${IMAGE_NAME}.rootfs.jffs2 \
+ IMAGE_CMD_jffs2 = "mkfs.jffs2 --root=${IMAGE_ROOTFS} --faketime \
+ --output=${IMGDEPLOYDIR}/${IMAGE_NAME}${IMAGE_NAME_SUFFIX}.jffs2 \
${EXTRA_IMAGECMD}"
You typically do not need to set this variable unless you are adding
--
2.25.1
next prev parent reply other threads:[~2021-06-14 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-14 5:30 [PATCH 0/2] Fixups for glossary Daniel Wagenknecht
2021-06-14 5:30 ` Daniel Wagenknecht [this message]
2021-06-14 5:30 ` [PATCH 2/2] ref-manual: variables: fixup class reference in IMAGE_MANIFEST Daniel Wagenknecht
2021-06-14 7:51 ` [docs] [PATCH 0/2] Fixups for glossary Michael Opdenacker
2021-06-14 8:12 ` Quentin Schulz
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=20210614053013.68669-2-dwagenknecht@emlix.com \
--to=dwagenknecht@emlix.com \
--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 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.