forked from luck/tmp_suning_uos_patched
4e4694d872
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> |
||
|---|---|---|
| .. | ||
| bad-array-space-comment.bconf | ||
| bad-array.bconf | ||
| bad-dotword.bconf | ||
| bad-empty.bconf | ||
| bad-keyerror.bconf | ||
| bad-longkey.bconf | ||
| bad-manywords.bconf | ||
| bad-mixed-kv1.bconf | ||
| bad-mixed-kv2.bconf | ||
| bad-no-keyword.bconf | ||
| bad-nonprintable.bconf | ||
| bad-samekey.bconf | ||
| bad-spaceword.bconf | ||
| bad-tree.bconf | ||
| bad-value.bconf | ||
| escaped.bconf | ||
| good-array-space-comment.bconf | ||
| good-comment-after-value.bconf | ||
| good-printables.bconf | ||
| good-simple.bconf | ||
| good-single.bconf | ||
| good-space-after-value.bconf | ||
| good-tree.bconf | ||