From: Robert Richter <rrichter@amd.com>
To: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>,
Jonathan Corbet <corbet@lwn.net>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] Documentation/kbuild: Document the kconfig choice default value
Date: Mon, 19 Jul 2021 22:20:57 +0200 [thread overview]
Message-ID: <YPXeqUV+22sxXS9y@rric.localdomain> (raw)
In-Reply-To: <YPVC0Xs0gRSywTO7@rric.localdomain>
On 19.07.21 11:16:09, Robert Richter wrote:
> @@ -417,8 +417,20 @@ definitions of that choice. If a [symbol] is associated to the choice,
> then you may define the same choice (i.e. with the same entries) in another
> place.
>
> -The default value of a choice is set to the first visible choice element.
> -Choice elements do not support the default attribute like menu entries do.
This patch was not properly rebased and does not apply. Will resend a v3.
Sorry for that.
-Robert
> +The default value of a choice is set to the first visible choice
> +element unless it is explicitly set by the 'default' property.
> +
> +Note:
> + Choice options do not support the 'default' attribute.
> +
> +E.g.::
> +
> + choice
> + default C1
> + config C0
> + config C1
> + # no default attribute here
> + endchoice
>
> comment::
>
> --
> 2.29.2
>
next prev parent reply other threads:[~2021-07-19 23:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ad9c50c54887bde41ae5de782248231c06a527c0.1626262835.git.rrichter@amd.com>
2021-07-15 9:26 ` [PATCH] Documentation: Fix intiramfs script name Robert Richter
2021-07-18 13:58 ` Masahiro Yamada
2021-07-15 9:26 ` [PATCH] Documentation/kbuild: Document the kconfig choice default value Robert Richter
2021-07-18 9:36 ` Masahiro Yamada
2021-07-19 9:16 ` [PATCH v2] " Robert Richter
2021-07-19 20:20 ` Robert Richter [this message]
2021-07-19 20:28 ` [PATCH v3] " Robert Richter
2021-08-05 12:47 ` Masahiro Yamada
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=YPXeqUV+22sxXS9y@rric.localdomain \
--to=rrichter@amd.com \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=michal.lkml@markovi.net \
/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