public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Legoll <vincent.legoll@gmail.com>
To: zippel@linux-m68k.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] - Add "def_bool" Kconfig format documentation
Date: Tue, 07 Aug 2007 00:29:40 +0200	[thread overview]
Message-ID: <1186439380.21014.9.camel@quad> (raw)

Hello,

here is a small documentation patch for the KConfig file format
"def_bool" type definition that was missing.

I hope the patch is not mangled...

>From 4742eb7a3169001304524e82a88ec1c94f70aa56 Mon Sep 17 00:00:00 2001
From: Vincent Legoll <vincent.legoll@gmail.com>
Date: Sat, 4 Aug 2007 16:50:06 +0200
Subject: [PATCH] - Add "def_bool" Kconfig format documentation


Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
---
 Documentation/kbuild/kconfig-language.txt |    8 ++++++++
 1 files changed, 8 insertions(+), 0 deletions(-)

diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
index 536d5bf..27b8af9 100644
--- a/Documentation/kbuild/kconfig-language.txt
+++ b/Documentation/kbuild/kconfig-language.txt
@@ -77,6 +77,14 @@ applicable everywhere (see syntax).
   Optionally, dependencies only for this default value can be added
with
   "if".
 
+- boolean type definition with a default value: "def_bool" <expr>
+  So these two examples are equivalent:
+  
+    def_bool <expr>
+  and
+    bool
+    default <expr>
+  
 - dependencies: "depends on"/"requires" <expr>
   This defines a dependency for this menu entry. If multiple
   dependencies are defined, they are connected with '&&'. Dependencies
-- 
1.5.2.4




             reply	other threads:[~2007-08-06 23:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-06 22:29 Vincent Legoll [this message]
2007-08-12  5:09 ` [PATCH] - Add "def_bool" Kconfig format documentation Randy Dunlap
2007-08-12  6:39   ` Robert P. J. Day
2007-08-13 11:12   ` Vincent Legoll

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=1186439380.21014.9.camel@quad \
    --to=vincent.legoll@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zippel@linux-m68k.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