From: Krzysztof Halasa <khc@intrepid.pm.waw.pl>
To: <linux-kernel@vger.kernel.org>
Subject: Re: RFC: configuring net interfaces
Date: 29 Mar 2001 13:29:32 +0200 [thread overview]
Message-ID: <m3u24c6cf7.fsf@intrepid.pm.waw.pl> (raw)
In-Reply-To: <Pine.LNX.4.30.0103281558140.15795-100000@intra.cyclades.com> <3AC27DB3.C2E20FC5@mandrakesoft.com>
In-Reply-To: Jeff Garzik's message of "Wed, 28 Mar 2001 19:11:31 -0500"
Jeff Garzik <jgarzik@mandrakesoft.com> writes:
> > Maybe it's a better idea to have just two ioctl's here (GET and SET), and
> > have "subioctl's" inside the structure passed to the HDLC layer (and
> > defined by the HDLC layer). This would allow changes in the HDLC layer
> > without having to change sockios.h (you'd still have to change HDLC's
> > code and definitions, but this would be more self-contained). Again, this
> > may be better, or maybe not. What do you think?
>
> That's essentially what's happening with ethtool
> (include/linux/ethtool.h in 2.4.3-pre8)
Right. While I don't think ethernet-only interface is our ultimate goal,
I'll look at it again to see if I can stole some idea there.
--
Krzysztof Halasa
Network Administrator
next prev parent reply other threads:[~2001-03-29 12:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3itkuq6xt.fsf@intrepid.pm.waw.pl>
2001-03-28 21:24 ` RFC: configuring net interfaces Ivan Passos
2001-03-29 0:11 ` Jeff Garzik
2001-03-28 21:53 ` Ivan Passos
2001-03-29 11:29 ` Krzysztof Halasa [this message]
2001-03-30 5:43 ` Jeff Garzik
2001-03-31 22:41 ` Krzysztof Halasa
2001-04-01 22:18 ` Jeff Garzik
2001-04-02 19:10 ` Krzysztof Halasa
2001-04-03 8:27 ` Francois Romieu
2001-04-03 13:07 ` Krzysztof Halasa
2001-04-04 8:18 ` Francois Romieu
2001-03-29 11:24 ` Krzysztof Halasa
[not found] ` <20010328182729.A16067@se1.cogenit.fr>
2001-03-28 23:03 ` Krzysztof Halasa
2001-03-29 0:13 ` Paul Fulghum
2001-03-29 10:34 ` Krzysztof Halasa
2001-03-29 9:25 ` Francois Romieu
2001-03-29 11:07 ` Krzysztof Halasa
2001-03-29 14:55 ` Paul Fulghum
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=m3u24c6cf7.fsf@intrepid.pm.waw.pl \
--to=khc@intrepid.pm.waw.pl \
--cc=linux-kernel@vger.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