netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: hadi@cyberus.ca
Cc: davem@redhat.com, xose@wanadoo.es, netdev@oss.sgi.com
Subject: Re: Level One LXT1001 GE chip
Date: Fri, 28 Nov 2003 02:14:39 +0100	[thread overview]
Message-ID: <20031128021439.0f48de70.ak@suse.de> (raw)
In-Reply-To: <1069941123.1027.6.camel@jzny.localdomain>

On 27 Nov 2003 08:52:03 -0500
jamal <hadi@cyberus.ca> wrote:

> Andi, is this the driver you were playing those neat tricks with
> getting rid of some of the nastiness in eth_type_trans()?

Yep.

I didn't attempt to NAPIize it though. Also it is still somewhat buggy.

-Andi

  reply	other threads:[~2003-11-28  1:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-26  1:02 Level One LXT1001 GE chip Xose Vazquez Perez
2003-11-27  9:03 ` David S. Miller
2003-11-27 11:20   ` Andi Kleen
2003-11-27 11:26     ` Andi Kleen
2003-11-27 13:52       ` jamal
2003-11-28  1:14         ` Andi Kleen [this message]
2003-11-27 15:22   ` Xose Vazquez Perez
2003-12-03  3:44     ` David S. Miller

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=20031128021439.0f48de70.ak@suse.de \
    --to=ak@suse.de \
    --cc=davem@redhat.com \
    --cc=hadi@cyberus.ca \
    --cc=netdev@oss.sgi.com \
    --cc=xose@wanadoo.es \
    /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).