From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: zippel@linux-m68k.org,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
kbuild-devel@lists.sourceforge.net
Subject: Re: [2.6 patch] kconfig: remove the unused "requires" syntax
Date: Mon, 18 Dec 2006 13:46:27 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0612181341090.28308@localhost.localdomain> (raw)
In-Reply-To: <20061218180447.GF10316@stusta.de>
On Mon, 18 Dec 2006, Adrian Bunk wrote:
> On Mon, Dec 18, 2006 at 11:41:59AM -0500, Robert P. J. Day wrote:
> >
> > Remove the note in the documentation that suggests people can use
> > "requires" for dependencies in Kconfig files.
> >...
>
> Considering that noone uses it, what about the patch below to also
> remove the implementation?
... big snip ...
i have no problem knocking out of the parser anything related to
"depends" or "requires." in fact, i did note in earlier patch
submissions that i was just cleaning the Kconfig files but i was
leaving the parser alone, and someone else was welcome to take care of
that.
if the kbuild folks are good with this, i certainly have no objection.
rday
p.s. i didn't look closely enough to see if your patch took out
support for both "depends" *and* "requires". at this point, neither
of those are necessary anymore -- it's all "depends on" except for
three remaining Kconfig files.
next prev parent reply other threads:[~2006-12-18 18:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-18 16:41 [PATCH] Remove suggestion that Kconfig files can use "requires" to list deps Robert P. J. Day
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 [this message]
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.0612181341090.28308@localhost.localdomain \
--to=rpjday@mindspring.com \
--cc=bunk@stusta.de \
--cc=kbuild-devel@lists.sourceforge.net \
--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
all inboxes | Powered by JetHome®