From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-19.4 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,INCLUDES_CR_TRAILER,INCLUDES_PATCH, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 84756C47083 for ; Wed, 2 Jun 2021 06:25:19 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6C26161376 for ; Wed, 2 Jun 2021 06:25:19 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231296AbhFBG1A (ORCPT ); Wed, 2 Jun 2021 02:27:00 -0400 Received: from mail.kernel.org ([198.145.29.99]:56376 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231285AbhFBG0y (ORCPT ); Wed, 2 Jun 2021 02:26:54 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id 5D25160FDC; Wed, 2 Jun 2021 06:25:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1622615111; bh=eMDGY00Srcwc9Mv3Q7xd4VTBuRrB8CH6Jc58EjqrkKE=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=URoAVkVnoiMQCTtI8p5lwYftSwz55U1gcEMPMxPExpodfp4lKLV6ylL9k/AeEDu36 dPErEFpLAiZMlMDoTj6E5WPZGrjFXkwogItB72hWo8QUdVgcXrVyWl/uyHkqa7fva9 eKob1UkBs9C6BVBi7lCA5k/N6fYpCtcuPtAn34YUGNnFHrIwbEdrEuugMZ/9QIBn16 WMdAFJLA621eEJs+IcXlootut3euhbAzzbmrknOhq7YWVjiIdB8jmVMzPbP500xlKc gfXjTFRbEFT+dmjtpdGC/5O3TAnnzKdV8hWNwGDIREKihItxaJC2sRkbkVUaXIhze7 ez+Eeh9JQuBOQ== From: Masami Hiramatsu To: Steven Rostedt Cc: Masami Hiramatsu , LKML , Ingo Molnar , Devin Moore Subject: [PATCH v3 5/6] docs: bootconfig: Update for mixing value and subkeys Date: Wed, 2 Jun 2021 15:25:08 +0900 Message-Id: <162261510788.255316.168529766501617432.stgit@devnote2> X-Mailer: git-send-email 2.25.1 In-Reply-To: <162261506232.255316.12147562546699211199.stgit@devnote2> References: <162261506232.255316.12147562546699211199.stgit@devnote2> User-Agent: StGit/0.19 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Update document for the mixing value and subkeys on a key. Signed-off-by: Masami Hiramatsu --- 0 files changed diff --git a/Documentation/admin-guide/bootconfig.rst b/Documentation/admin-guide/bootconfig.rst index 452b7dcd7f6b..37bdae273b18 100644 --- a/Documentation/admin-guide/bootconfig.rst +++ b/Documentation/admin-guide/bootconfig.rst @@ -89,13 +89,33 @@ you can use ``+=`` operator. For example:: In this case, the key ``foo`` has ``bar``, ``baz`` and ``qux``. -However, a sub-key and a value can not co-exist under a parent key. -For example, following config is NOT allowed.:: +Moreover, sub-keys and a value can co-exist under a parent key. +For example, following config is allowed.:: foo = value1 - foo.bar = value2 # !ERROR! subkey "bar" and value "value1" can NOT co-exist - foo.bar := value2 # !ERROR! even with the override operator, this is NOT allowed. + foo.bar = value2 + foo := value3 # This will update foo's value. +Note, since there is no syntax to add raw value in the structured +key, you have to define it outside of the brace. For example:: + + foo.bar = value1 + foo.bar { + baz = value2 + qux = value3 + } + +Also, the order of the value node under a key is fixed. If there +are a value and subkeys, the value is always the first child node +of the key. Thus if user specifies subkeys first, e.g.:: + + foo.bar = value1 + foo = value2 + +In the program (and /proc/bootconfig), it will be shown as below:: + + foo = value2 + foo.bar = value1 Comments --------