From: Pete Popov <ppopov@mvista.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Linux MIPS mailing list <linux-mips@linux-mips.org>
Subject: Re: Au1000 ethernet patch
Date: 28 Mar 2003 15:48:24 -0800 [thread overview]
Message-ID: <1048895304.29891.8.camel@zeus.mvista.com> (raw)
In-Reply-To: <20030329004153.A20126@linux-mips.org>
On Fri, 2003-03-28 at 15:41, Ralf Baechle wrote:
> On Fri, Mar 28, 2003 at 02:37:48PM -0800, Pete Popov wrote:
>
> > On Fri, 2003-03-28 at 11:14, Hartvig Ekner wrote:
> > > The following patch fixes an error where ethernet minimum packets are 4 bytes too long. This caused certain
> > > devices not to respond to ARP requests (which is a bug on their side as well, but.....).
> >
> >
> > Thanks, I'll apply it later tonight.
>
> <asm/if_ether.h> already defines the constant ETH_ZLEN for this purpose.
Great, thanks. I'll make the correction.
Pete
prev parent reply other threads:[~2003-03-28 23:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-28 19:14 Au1000 ethernet patch Hartvig Ekner
2003-03-28 22:37 ` Pete Popov
2003-03-28 23:41 ` Ralf Baechle
2003-03-28 23:48 ` Pete Popov [this message]
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=1048895304.29891.8.camel@zeus.mvista.com \
--to=ppopov@mvista.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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