mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Adrian Bunk <bunk@kernel.org>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	lkml <linux-kernel@vger.kernel.org>,
	akpm <akpm@linux-foundation.org>,
	sam@ravnborg.org, zippel@linux-m68k.org,
	vincent.legoll@gmail.com
Subject: Re: [PATCH] kconfig: update kconfig-language text
Date: Mon, 13 Aug 2007 15:13:30 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708131510140.14058@localhost.localdomain> (raw)
In-Reply-To: <20070813185431.GD18945@stusta.de>

On Mon, 13 Aug 2007, Adrian Bunk wrote:

> On Mon, Aug 13, 2007 at 11:38:09AM -0700, Randy Dunlap wrote:
> > From: Randy Dunlap <randy.dunlap@oracle.com>
> >
> > Add kconfig-language docs for mainmenu, def_bool[ean],
> > and def_tristate.
> >
> > Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> > Signed-off-by: Vincent Legoll <vincent.legoll@gmail.com>
> > ---
> >  Documentation/kbuild/kconfig-language.txt |   12 ++++++++++++
> >  1 file changed, 12 insertions(+)
> >
> > --- linux-2.6.23-rc3.orig/Documentation/kbuild/kconfig-language.txt
> > +++ linux-2.6.23-rc3/Documentation/kbuild/kconfig-language.txt
> > @@ -77,6 +77,11 @@ applicable everywhere (see syntax).
> >    Optionally, dependencies only for this default value can be added with
> >    "if".
> >
> > +- type definition + default value:
> > +	"def_bool"/"def_boolean"/"def_tristate" <expr> ["if" <expr>]
> >...
>
> Should the redundant and unused def_boolean be documented or removed?
>
> I'd prefer the latter.

me too.  and, as i've suggested before, it would also be cleaner to
remove the redundant "requires" and almost redundant "depends" from
Kconfig files, and standardize exclusively on "depends on".

at the moment, there are only five Kconfig files that use the far less
common "depends" directive:

./drivers/telephony/Kconfig:    depends ISA || PCI
./drivers/leds/Kconfig: depends LEDS_CLASS && ARCH_H1940
./drivers/input/misc/Kconfig:   depends EXPERIMENTAL
./arch/blackfin/Kconfig:        depends BFIN_DMA_5XX
./arch/powerpc/platforms/Kconfig:       depends PPC_IBM_CELL_BLADE

adjust those and there's no reason to hang on to "depends" any longer.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  parent reply	other threads:[~2007-08-13 19:21 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13 18:38 Randy Dunlap
2007-08-13 18:54 ` Adrian Bunk
2007-08-13 19:05   ` Randy Dunlap
2007-08-13 19:13   ` Robert P. J. Day [this message]
2007-08-13 19:43     ` Randy Dunlap
2007-08-13 19:44       ` Robert P. J. Day
2007-08-13 20:05     ` [-mm patch] kconfig syntax cleanups Adrian Bunk
2007-08-13 21:17       ` Randy Dunlap
2007-08-13 21:31         ` Adrian Bunk
2007-10-19 17:53   ` [PATCH v3] kconfig: update kconfig-language text Randy Dunlap
2007-10-19 19:59     ` Sam Ravnborg

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=Pine.LNX.4.64.0708131510140.14058@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=sam@ravnborg.org \
    --cc=vincent.legoll@gmail.com \
    --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

all inboxes | Powered by JetHome®