From: "Randy.Dunlap" <rddunlap@osdl.org>
To: lkml <linux-kernel@vger.kernel.org>
Cc: niv@us.ibm.com, benh@kernel.crashing.org, davem@redhat.com,
netdev@oss.sgi.com
Subject: Re: [patch/RFC] networking menus
Date: Sun, 14 Mar 2004 20:54:38 -0800 [thread overview]
Message-ID: <20040314205438.3d7bcd34.rddunlap@osdl.org> (raw)
In-Reply-To: <20040314190724.1af1f11d.rddunlap@osdl.org>
On Sun, 14 Mar 2004 19:07:24 -0800 "Randy.Dunlap" <rddunlap@osdl.org> wrote:
| On Sun, 14 Mar 2004 18:17:17 -0800 Nivedita Singhvi <niv@us.ibm.com> wrote:
|
| | Randy.Dunlap wrote:
| |
| | > This is just a first pass/RFC. It moves "Networking support" out of
| | > the "Device Drivers" menu, which seems helpful to me. However,
| | > ISTM that it should really just be the "Networking options" here
| | > and not include Amateur Radio, IrDA, and Bluetooth support.
| | > I.e., I think that those latter 3 should fall under Device Drivers.
| | > Does that make sense to anyone else?
| |
| | Just a comment that those 3 subsystems are not just
| | device drivers, they have non-trivial amount of code
| | in the protocol stack under ../net/. So would moving
| | them to device drivers be misleading in any way?
| |
| | I can see pulling out Networking support from under
| | device drivers, though.
|
| Agreed, I looked again and those 3 should stay under
| "Networking support." I'm still looking for other items
| to move to make it all easier to navigate.
Does it make sense to anyone besides me to move protocol-related
modules like SLIP, PPP, and PLIP from Device Drivers/Network device(s)
to "Networking support"?
They feel more like protocols than device drivers to me....
| | > Does this need to be discussed on netdev (also)?
| |
| | Yes. :)
|
| OK. Thanks for cc-ing it.
|
| | thanks,
| | Nivedita
--
~Randy
next prev parent reply other threads:[~2004-03-15 4:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 0:33 [patch/RFC] networking menus Randy.Dunlap
2004-03-15 2:17 ` Nivedita Singhvi
2004-03-15 3:07 ` Randy.Dunlap
2004-03-15 4:54 ` Randy.Dunlap [this message]
2004-03-16 11:01 ` Ingo Oeser
2004-03-15 3:02 ` Jeff Garzik
2004-03-15 22:24 ` PATCH] networking menus v2 Randy.Dunlap
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=20040314205438.3d7bcd34.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=niv@us.ibm.com \
/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).