| To: | Jeff Garzik <jgarzik@xxxxxxxxx> |
|---|---|
| Subject: | Re: [PATCH] ethtool_ops rev 4 |
| From: | "David S. Miller" <davem@xxxxxxxxxx> |
| Date: | Fri, 1 Aug 2003 16:01:36 -0700 |
| Cc: | willy@xxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <3F2AF141.2010308@pobox.com> |
| References: | <20030801150232.GV22222@parcelfarce.linux.theplanet.co.uk> <20030801154021.GA7696@gtf.org> <20030801154656.GW22222@parcelfarce.linux.theplanet.co.uk> <20030801162536.GA18574@gtf.org> <20030801132037.3f3542ae.davem@redhat.com> <3F2AE91D.5090705@pobox.com> <20030801153255.204baf66.davem@redhat.com> <3F2AF141.2010308@pobox.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Fri, 01 Aug 2003 19:01:21 -0400 Jeff Garzik <jgarzik@xxxxxxxxx> wrote: > A DO_ETHTOOL_OPS macro in the driver's ->do_ioctl -- intentionally not > included in the kernel -- does the rest, I don't understand. Where does this DO_ETHTOOL_OPS macro come from? Is it defined by kcompat? If so, how will drivers in vanilla 2.4.x trees end up with the DO_ETHTOOL_OPS define? |
| Previous by Date: | Re: [PATCH] ethtool_ops rev 4, Jeff Garzik |
|---|---|
| Next by Date: | Re: [PATCH] ethtool_ops rev 4, David S. Miller |
| Previous by Thread: | Re: [PATCH] ethtool_ops rev 4, Jeff Garzik |
| Next by Thread: | Re: [PATCH] ethtool_ops rev 4, Jeff Garzik |
| Indexes: | [Date] [Thread] [Top] [All Lists] |