From: Markus Heidelberg via ptxdist <ptxdist@pengutronix.de>
To: <ptxdist@pengutronix.de>
Cc: Markus Heidelberg <m.heidelberg@cab.de>
Subject: [ptxdist] [PATCH] doc: fix rule file examples regarding suboptions
Date: Tue, 13 Jan 2026 09:43:00 +0100 [thread overview]
Message-ID: <20260113084523.88722-1-m.heidelberg@cab.de> (raw)
Signed-off-by: Markus Heidelberg <m.heidelberg@cab.de>
---
doc/dev_advanced_rule_files.rst | 20 +++++++++++---------
1 file changed, 11 insertions(+), 9 deletions(-)
diff --git a/doc/dev_advanced_rule_files.rst b/doc/dev_advanced_rule_files.rst
index 26abf214d..55dc0e8f0 100644
--- a/doc/dev_advanced_rule_files.rst
+++ b/doc/dev_advanced_rule_files.rst
@@ -91,15 +91,17 @@ let’s expand our menu. Here is its current content:
FIXME
We’ll add two menu entries, one for each optional parameter we want to
-add on demand to the ``configure`` parameters:
+add on demand to the ``configure`` parameters. The main menu entry will be
+adapted to contain these entries in a submenu, trailing spaces are added to the
+``prompt`` string for proper alignment:
.. code-block:: kconfig
## SECTION=project_specific
- config FOO
+ menuconfig FOO
tristate
- prompt "foo"
+ prompt "foo "
help
FIXME
@@ -230,10 +232,10 @@ file looks like:
## SECTION=project_specific
- config FOO
+ menuconfig FOO
tristate
select ZLIB
- prompt "foo"
+ prompt "foo "
help
FIXME
@@ -269,11 +271,11 @@ enabled. To add these dependencies on demand, the menu file looks like:
## SECTION=project_specific
- config FOO
+ menuconfig FOO
tristate
select ZLIB if FOO_FOO
select LIBXML2 if FOO_BAR
- prompt "foo"
+ prompt "foo "
help
FIXME
@@ -322,12 +324,12 @@ file. With all the additions above it now looks like:
## SECTION=project_specific
- config FOO
+ menuconfig FOO
tristate
select ZLIB if FOO_FOO
select LIBXML2 if FOO_BAR
select LIBC_M
- prompt "foo"
+ prompt "foo "
help
FIXME
--
2.43.0
reply other threads:[~2026-01-13 8:46 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=20260113084523.88722-1-m.heidelberg@cab.de \
--to=ptxdist@pengutronix.de \
--cc=m.heidelberg@cab.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