From: SangYuhiter <sangyu.code@gmail.com>
To: linux-kbuild@vger.kernel.org
Cc: masahiroy@kernel.org, linux-doc@vger.kernel.org,
SangYuhiter <sangyu.code@gmail.com>
Subject: [PATCH] Documentation: kbuild: fix typo in kconfig-language.rst
Date: Mon, 20 Jun 2022 01:03:37 +0800 [thread overview]
Message-ID: <20220619170337.24743-1-sangyu.code@gmail.com> (raw)
change "default y/m" to "default y/n"
add " should be "default y" " in default section d)
Signed-off-by: SangYuhiter <sangyu.code@gmail.com>
---
Documentation/kbuild/kconfig-language.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/kbuild/kconfig-language.rst b/Documentation/kbuild/kconfig-language.rst
index a7173843a294..ae3add11d5e7 100644
--- a/Documentation/kbuild/kconfig-language.rst
+++ b/Documentation/kbuild/kconfig-language.rst
@@ -92,7 +92,7 @@ applicable everywhere (see syntax).
release to release.
Note:
- Things that merit "default y/m" include:
+ Things that merit "default y/n" include:
a) A new Kconfig option for something that used to always be built
should be "default y".
@@ -105,7 +105,7 @@ applicable everywhere (see syntax).
"default n". This allows you to provide sane defaults.
d) Hardware or infrastructure that everybody expects, such as CONFIG_NET
- or CONFIG_BLOCK. These are rare exceptions.
+ or CONFIG_BLOCK, should be "default y". These are rare exceptions.
- type definition + default value::
--
2.17.1
next reply other threads:[~2022-06-19 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-19 17:03 SangYuhiter [this message]
2022-06-19 17:06 ` [PATCH] Documentation: kbuild: fix typo in kconfig-language.rst Randy Dunlap
2022-06-19 19:12 ` Matthew Wilcox
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=20220619170337.24743-1-sangyu.code@gmail.com \
--to=sangyu.code@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox