From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: ioe-lkml@axxeo.de, matthew@wil.cx,
lkml <linux-kernel@vger.kernel.org>,
netdev@oss.sgi.com, hadi@cyberus.ca, cfriesen@nortel.com,
tgraf@suug.ch
Subject: Re: [RFC/PATCH] network configs: disconnect network options from drivers
Date: Thu, 31 Mar 2005 12:02:13 -0800 [thread overview]
Message-ID: <424C5745.7020501@osdl.org> (raw)
In-Reply-To: <20050331185226.GA8146@mars.ravnborg.org>
Sam Ravnborg wrote:
> On Wed, Mar 30, 2005 at 11:47:09PM -0800, Randy.Dunlap wrote:
>
>>- some Networking options need to be qualified with CONFIG_NET
>
> You can something along the lines os:
>
> menu "Networking options and protocols"
>
> config NET
> bool "Networking support"
> default y
>
> if NET
>
> ...
>
> menu "Network device support"
> ...
> endmenu
>
> ...
>
> endif
> endmenu
>
> Then everything wrapped in between if NET/endif is dependent on NET
> without stating this explicitly.
> You will alos have the menu nice indented.
Yes, sounds good, thanks.
And I'll look into Thomas's suggestions.
Other than "sounds good," are there some comments on:
a. leaving IrDA and Bluetooth subsystem (with drivers) where they
are, which is under "Network options and protocols"
(I really don't want to split their drivers away from their
subsystem, just to put them under Network driver support.)
b. leaving SLIP, PPP, and PLIP where they are under Network driver
support, even though they say that they are "protocols" ?
Any others?
Thanks,
--
~Randy
next prev parent reply other threads:[~2005-03-31 20:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 7:47 [RFC/PATCH] network configs: disconnect network options from drivers Randy.Dunlap
2005-03-31 11:04 ` jamal
2005-03-31 16:46 ` Chris Friesen
2005-03-31 18:30 ` David S. Miller
2005-03-31 18:22 ` Thomas Graf
2005-03-31 18:52 ` Sam Ravnborg
2005-03-31 20:02 ` Randy.Dunlap [this message]
2005-03-31 20:30 ` Sam Ravnborg
2005-04-04 3:30 ` [PATCH] " Randy.Dunlap
2005-04-04 19:50 ` Sam Ravnborg
2005-04-04 20:48 ` Randy.Dunlap
2005-04-04 21:55 ` Sam Ravnborg
2005-04-04 23:11 ` Randy.Dunlap
2005-04-05 15:45 ` Sam Ravnborg
2005-04-05 18:46 ` Randy.Dunlap
2005-04-05 21:11 ` [PATCH] networking: restructuring of net/ kconfig Sam Ravnborg
2005-04-05 17:42 ` [PATCH] network configs: disconnect network options from drivers Sridhar Samudrala
2005-04-05 21:04 ` 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=424C5745.7020501@osdl.org \
--to=rddunlap@osdl.org \
--cc=cfriesen@nortel.com \
--cc=hadi@cyberus.ca \
--cc=ioe-lkml@axxeo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=netdev@oss.sgi.com \
--cc=sam@ravnborg.org \
--cc=tgraf@suug.ch \
/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;
as well as URLs for NNTP newsgroup(s).