From: "David S. Miller" <davem@redhat.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: pp@ee.oulu.fi, netdev@oss.sgi.com
Subject: Re: changing MTU on b44 breaks eth0
Date: Wed, 5 Nov 2003 13:35:16 -0800 [thread overview]
Message-ID: <20031105133516.289a62b9.davem@redhat.com> (raw)
In-Reply-To: <3FA96D68.4090806@pobox.com>
On Wed, 05 Nov 2003 16:36:40 -0500
Jeff Garzik <jgarzik@pobox.com> wrote:
> If someone can send me the latest patch, certainly! :)
>
> There wasn't a patch appended to this message I'm replying to, nor did
> any of the patches I saw on netdev include a SET_NETDEV_DEV change...
The most recent one did, I'll forward to you under seperate
cover.
next prev parent reply other threads:[~2003-11-05 21:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1067888106.3366.20.camel@bluez.bueche.ch>
2003-11-03 20:53 ` changing MTU on b44 breaks eth0 Pekka Pietikainen
2003-11-03 23:16 ` David S. Miller
2003-11-04 11:15 ` Pekka Pietikainen
2003-11-04 17:13 ` David S. Miller
2003-11-04 21:19 ` Pekka Pietikainen
2003-11-04 21:20 ` David S. Miller
2003-11-05 21:36 ` Jeff Garzik
2003-11-05 21:35 ` David S. Miller [this message]
2003-11-06 22:02 ` Charles Bueche
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=20031105133516.289a62b9.davem@redhat.com \
--to=davem@redhat.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=pp@ee.oulu.fi \
/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).