mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>
Cc: trivial@kernel.org
Subject: [PATCH] Remove suggestion that Kconfig files can use "requires" to list deps
Date: Mon, 18 Dec 2006 11:41:59 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0612181138360.27491@localhost.localdomain> (raw)


  Remove the note in the documentation that suggests people can use
"requires" for dependencies in Kconfig files.

Signed-off-by: Robert P. J. Day <rpjday@mindspring.com>

---

  at this point, AFAICT, all Kconfig files now use "depends on"
exclusively, except for three that still use "depends", but i've
already submitted a patch for that that should be in the pipeline
somewhere.


diff --git a/Documentation/kbuild/kconfig-language.txt b/Documentation/kbuild/kconfig-language.txt
index 536d5bf..658abb5 100644
--- a/Documentation/kbuild/kconfig-language.txt
+++ b/Documentation/kbuild/kconfig-language.txt
@@ -77,7 +77,7 @@ applicable everywhere (see syntax).
   Optionally, dependencies only for this default value can be added with
   "if".

-- dependencies: "depends on"/"requires" <expr>
+- dependencies: "depends on" <expr>
   This defines a dependency for this menu entry. If multiple
   dependencies are defined, they are connected with '&&'. Dependencies
   are applied to all other options within this menu entry (which also

             reply	other threads:[~2006-12-18 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-18 16:41 Robert P. J. Day [this message]
2006-12-18 18:04 ` [2.6 patch] kconfig: remove the unused "requires" syntax Adrian Bunk
2006-12-18 18:46   ` Robert P. J. Day
2006-12-18 19:31     ` Adrian Bunk
2006-12-18 19:38       ` Robert P. J. Day
2006-12-19 17:53   ` Roman Zippel
2006-12-28 21:05     ` Adrian Bunk
2007-01-01 19:08       ` Roman Zippel

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.0612181138360.27491@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trivial@kernel.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®