From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: netdev_ops?
Date: Tue, 22 Jul 2003 22:30:10 -0700 [thread overview]
Message-ID: <3F1E1D62.90009@candelatech.com> (raw)
In-Reply-To: <20030722220745.379a73c6.davem@redhat.com>
David S. Miller wrote:
> On Tue, 22 Jul 2003 22:06:04 -0700
> Ben Greear <greearb@candelatech.com> wrote:
>
>
>>Any progress towards getting the netdev_ops into 2.4?
>>
>>I have several patches that would benefit (in that no new ioctls
>>would be needed) if this goes in.
>
>
> If anything, it's going to go into 2.6.x first, and then backported
> to 2.4.x after it's had a few months of testing and tweaking.
>
Any interest in a lower-risk netdev-ops lite? I have a relatively
ugly little patch that will allow me to handle certain ETHTOOL ioctls in
dev.c's ioctl handling code. Ugly, but short, and very little chance of
breaking anything else....
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2003-07-23 5:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-23 5:06 netdev_ops? Ben Greear
2003-07-23 5:07 ` netdev_ops? David S. Miller
2003-07-23 5:30 ` Ben Greear [this message]
2003-07-23 6:02 ` netdev_ops? David S. Miller
2003-07-23 6:24 ` netdev_ops? Ben Greear
2003-07-23 6:27 ` netdev_ops? David S. Miller
2003-07-23 6:36 ` netdev_ops? Ben Greear
2003-07-23 7:01 ` netdev_ops? David S. Miller
2003-07-23 7:28 ` netdev_ops? Ben Greear
2003-07-23 7:34 ` netdev_ops? David S. Miller
2003-07-23 8:08 ` netdev_ops? Ben Greear
2003-07-23 8:15 ` netdev_ops? David S. Miller
2003-07-23 16:59 ` netdev_ops? Jeff Garzik
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=3F1E1D62.90009@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.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).