summaryrefslogtreecommitdiff
path: root/Documentation/admin-guide/bootconfig.rst
diff options
context:
space:
mode:
authorMasami Hiramatsu <mhiramat@kernel.org>2020-02-21 11:13:42 +0300
committerSteven Rostedt (VMware) <rostedt@goodmis.org>2020-02-21 17:59:19 +0300
commit4e4694d8729f7cd6381f6691e8f83e378fce3160 (patch)
treeb7c07e9ddd7681384ee330e6f8c64273c3ed52ec /Documentation/admin-guide/bootconfig.rst
parent88b913718db94697497028b85acbec8b180a4333 (diff)
downloadlinux-4e4694d8729f7cd6381f6691e8f83e378fce3160.tar.xz
bootconfig: Prohibit re-defining value on same key
Currently, bootconfig adds a new value on the existing key to the tail of an array. But this looks a bit confusing because an admin can easily rewrite the original value in the same config file. This rejects the following value re-definition. key = value1 ... key = value2 You should rewrite value1 to value2 in this case. Link: http://lkml.kernel.org/r/158227282199.12842.10110929876059658601.stgit@devnote2 Suggested-by: Steven Rostedt (VMware) <rostedt@goodmis.org> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org> [ Fixed spelling of arraies to arrays ] Signed-off-by: Steven Rostedt (VMware) <rostedt@goodmis.org>
Diffstat (limited to 'Documentation/admin-guide/bootconfig.rst')
-rw-r--r--Documentation/admin-guide/bootconfig.rst11
1 files changed, 10 insertions, 1 deletions
diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst
index dfeffa73dca3..57119fb69d36 100644
--- a/Documentation/admin-guide/bootconfig.rst
+++ b/Documentation/admin-guide/bootconfig.rst
@@ -62,7 +62,16 @@ Or more shorter, written as following::
In both styles, same key words are automatically merged when parsing it
at boot time. So you can append similar trees or key-values.
-Note that a sub-key and a value can not co-exist under a parent key.
+Same-key Values
+---------------
+
+It is prohibited that two or more values or arrays share a same-key.
+For example,::
+
+ foo = bar, baz
+ foo = qux # !ERROR! we can not re-define same key
+
+Also, a sub-key and a value can not co-exist under a parent key.
For example, following config is NOT allowed.::
foo = value1