From: Prasad Pandit <pjp@fedoraproject.org>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: "linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: Re: [PATCH v1] kconfig: add config and source entry details
Date: Wed, 17 Apr 2024 06:29:29 +0000 (UTC) [thread overview]
Message-ID: <668901914.114470.1713335369416@mail.yahoo.com> (raw)
In-Reply-To: <CAK7LNASZR=n+T=9Lo-5=Nw9WTwY9ywdTNvAUdt8xDXxsnNu3Tg@mail.gmail.com>
Hello Masahiro,
On Tuesday, 16 April, 2024 at 05:19:40 pm IST, Masahiro Yamada <masahiroy@kernel.org> wrote:>
>You added
>
>- indented by a leading tab (\t) character,
>- Help text is further indented by two more spaces.
>
>These are recommended coding styles for readability,
>not grammatical requirements.
-> https://www.kernel.org/doc/html/latest/kbuild/kconfig-language.html
* I see, thank you for the clarification. Reading this language reference and seeing the config entries consistently using indentation in Kconfig files, I mistook it as language syntax.
* Maybe it'll help to explicitly specify that indentation is not the Kconfig language syntax.
>You can write Kconfig code without indentation,
>without blank lines in-between.
>
>
>config FOO
>bool "foo"
>depends on BAR
>config BAR
>bool "bar"
>config BAZ
>bool "baz"
>
>
>It is unreadable, but it works fine.
>
>
>Only the place where the indentation plays an act
>is the end of help. It is already documented.
>
> The end of the help text is determined by
> the indentation level, this means it ends at the first line which has
> a smaller indentation than the first line of the help text.
>
* Got it. In that case, to confirm: are there any input cases which are erroneous according to the Kconfig language syntax? Because even config entries ending with an 'EOF' are not flagged as an error.
* Last to confirm: is 'kconfig-language.html' reference for the Kconfig langauge as implemented in kernel OR it is the general language reference that applies to all Kconfig files across all projects? Because non-kernel projects also seem to use Kconfig files.
Thank you.
---
- Prasad
next prev parent reply other threads:[~2024-04-17 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-07 7:29 [PATCH v1] kconfig: add config and source entry details Prasad Pandit
2024-04-16 6:50 ` Prasad Pandit
2024-04-16 11:48 ` Masahiro Yamada
2024-04-17 6:29 ` Prasad Pandit [this message]
2024-04-20 7:24 ` Masahiro Yamada
2024-04-23 6:16 ` Prasad Pandit
2024-04-23 10:10 ` Masahiro Yamada
2024-04-24 5:25 ` Prasad Pandit
2024-04-26 19:21 ` Masahiro Yamada
2024-04-30 7:36 ` Prasad Pandit
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=668901914.114470.1713335369416@mail.yahoo.com \
--to=pjp@fedoraproject.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=pj.pandit@yahoo.in \
/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