From: Don Fry <brazilnut@us.ibm.com>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: netdev@vger.kernel.org
Subject: Re: [RFT PATCH] pcnet32: NAPI support
Date: Wed, 28 Jun 2006 09:55:41 -0700 [thread overview]
Message-ID: <20060628165541.GA16601@us.ibm.com> (raw)
In-Reply-To: <20060628144010.GA1446@csclub.uwaterloo.ca>
On Wed, Jun 28, 2006 at 10:40:10AM -0400, Lennart Sorensen wrote:
> On Fri, Jun 23, 2006 at 02:32:12PM -0700, Don Fry wrote:
> > This set of changes combines the work done by Len Sorensen and myself to
> > add compile time support for NAPI for the pcnet32 driver. I have tested
> > it on ia32 and ppc64 hardware with various versions of the pcnet32
> > adapter. I have also made a few changes requested by Jon Mason, but the
> > substitution of the many magic numbers in the driver is not yet done.
> >
> > If no-one encounters any problems when testing this, I will break up the
> > several changes, into proper patches and submit them next week.
>
> Well so far this is working for me. It is a somewhat different layout
> of the interrupt handler so it took me a bit of work to get the features
> I need patched in, but in the end I ended up with simpler code as a
> reesult, so I am quite happy with the new layout. The driver works on
> everything I have to try it on so far.
>
<snip>
Yes, I saw the debug statements when creating the email and was too lazy
to remove them and create a new patch. The patch needs to be broken up
into functional pieces anyway, so since it has passed all of my testing
as well, I will start on that...
>
> So yep, looks pretty good to me. Those two debug statements are my only
> comments on it.
>
> Len Sorensen
--
Don Fry
brazilnut@us.ibm.com
next prev parent reply other threads:[~2006-06-28 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-23 21:32 [RFT PATCH] pcnet32: NAPI support Don Fry
2006-06-28 14:40 ` Lennart Sorensen
2006-06-28 16:55 ` Don Fry [this message]
2006-06-29 12:58 ` Lennart Sorensen
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=20060628165541.GA16601@us.ibm.com \
--to=brazilnut@us.ibm.com \
--cc=lsorense@csclub.uwaterloo.ca \
--cc=netdev@vger.kernel.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).