From: Quentin Schulz <foss+yocto@0leil.net>
To: bitbake-devel@lists.openembedded.org
Cc: docs@lists.yoctoproject.org, Quentin Schulz <quentin.schulz@cherry.de>
Subject: [PATCH] doc: bitbake-user-manual-metadata: fix missing whitespace around '=' operator
Date: Thu, 30 Jul 2026 16:47:58 +0200 [thread overview]
Message-ID: <20260730-doc-space-v1-1-90ccb2357b2b@cherry.de> (raw)
From: Quentin Schulz <quentin.schulz@cherry.de>
Since Whinlatter (5.3) BitBake will warn if the assignment operator (=)
isn't surrounded by spaces, so let's fix the only occurrence in the docs
where it was not already the case.
Signed-off-by: Quentin Schulz <quentin.schulz@cherry.de>
---
Inspired by https://lore.kernel.org/yocto-docs/20260728090746.27793-4-niko.mauno@vaisala.com/
for yocto-docs.
---
doc/bitbake-user-manual/bitbake-user-manual-metadata.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
index 0c7c3ff99..068ea2afb 100644
--- a/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
+++ b/doc/bitbake-user-manual/bitbake-user-manual-metadata.rst
@@ -617,8 +617,8 @@ variable.
``KERNEL_FEATURES`` variable based on the architecture::
KERNEL_FEATURES:append = " ${KERNEL_EXTRA_FEATURES}"
- KERNEL_FEATURES:append:qemux86=" cfg/sound.scc cfg/paravirt_kvm.scc"
- KERNEL_FEATURES:append:qemux86-64=" cfg/sound.scc cfg/paravirt_kvm.scc"
+ KERNEL_FEATURES:append:qemux86 = " cfg/sound.scc cfg/paravirt_kvm.scc"
+ KERNEL_FEATURES:append:qemux86-64 = " cfg/sound.scc cfg/paravirt_kvm.scc"
- *Setting a Variable for a Single Task:* BitBake supports setting a
variable just for the duration of a single task. Here is an example::
---
base-commit: d1886335f0d7fa86e87c6001d5be306a8e90586b
change-id: 20260730-doc-space-886498d58e08
Best regards,
--
Quentin Schulz <quentin.schulz@cherry.de>
reply other threads:[~2026-07-30 14:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260730-doc-space-v1-1-90ccb2357b2b@cherry.de \
--to=foss+yocto@0leil.net \
--cc=bitbake-devel@lists.openembedded.org \
--cc=docs@lists.yoctoproject.org \
--cc=quentin.schulz@cherry.de \
/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