From: Jeff Garzik <jgarzik@pobox.com>
To: Matthew Wilcox <willy@debian.org>
Cc: netdev@oss.sgi.com
Subject: Re: [PATCH] Move eth_mac_addr and eth_change_mtu
Date: Fri, 11 Jul 2003 17:17:03 -0400 [thread overview]
Message-ID: <3F0F294F.4060804@pobox.com> (raw)
In-Reply-To: <20030711210522.GM20424@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Fri, Jul 11, 2003 at 04:57:21PM -0400, Jeff Garzik wrote:
>
>>Well, I don't see/understand this next-stage, so elaboration would be
>>nice. As-is, I do not support merging this patch.
>
>
> It's the next stage you're calling for -- move these functions:
>
> dev->change_mtu = eth_change_mtu;
> dev->hard_header = eth_header;
> dev->rebuild_header = eth_rebuild_header;
> dev->set_mac_address = eth_mac_addr;
> dev->hard_header_cache = eth_header_cache;
> dev->header_cache_update= eth_header_cache_update;
> dev->hard_header_parse = eth_header_parse;
>
> into netdev_ops. Which means each driver will need to see them.
Drivers don't need to see them now, they shouldn't need to see them
after netdev_ops.
It's hidden by ether_setup.
> I thought I could justify moving these functions already on the grounds
> that if you were looking for the definition of eth_change_mtu(),
> net_init.c would be a much less likely place to look than
> net/ethernet/eth.c
If you're gonna do that, move all of ether_setup, alloc_etherdev, etc.
Don't just move two out of ~10 functions.
Jeff
next prev parent reply other threads:[~2003-07-11 21:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 18:19 [PATCH] Move eth_mac_addr and eth_change_mtu Matthew Wilcox
2003-07-11 18:23 ` Jeff Garzik
2003-07-11 18:25 ` Matthew Wilcox
2003-07-11 20:57 ` Jeff Garzik
2003-07-11 21:05 ` Matthew Wilcox
2003-07-11 21:17 ` Jeff Garzik [this message]
2003-07-11 21:56 ` Matthew Wilcox
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=3F0F294F.4060804@pobox.com \
--to=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=willy@debian.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.