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 16:57:21 -0400 [thread overview]
Message-ID: <3F0F24B1.5050200@pobox.com> (raw)
In-Reply-To: <20030711182530.GH20424@parcelfarce.linux.theplanet.co.uk>
Matthew Wilcox wrote:
> On Fri, Jul 11, 2003 at 02:23:30PM -0400, Jeff Garzik wrote:
>
>>On Fri, Jul 11, 2003 at 07:19:46PM +0100, Matthew Wilcox wrote:
>>
>>>Move eth_mac_addr() and eth_change_mtu() from drivers/net/net_init.c
>>>to net/ethernet/eth.c
>>
>>Why? It's not used outside of net_init.c AFAICS.
>
>
> Preparation for the next stage of netdev_ops
Well, I don't see/understand this next-stage, so elaboration would be
nice. As-is, I do not support merging this patch.
Jeff
next prev parent reply other threads:[~2003-07-11 20:57 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 [this message]
2003-07-11 21:05 ` Matthew Wilcox
2003-07-11 21:17 ` Jeff Garzik
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=3F0F24B1.5050200@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 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).