public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "David S. Miller" <davem@redhat.com>
Cc: linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: Updated zerocopy patch up on kernel.org
Date: Tue, 09 Jan 2001 20:23:17 -0500	[thread overview]
Message-ID: <3A5BB985.8A249BE1@mandrakesoft.com> (raw)
In-Reply-To: <200101100055.QAA07674@pizda.ninka.net>

"David S. Miller" wrote:
> 
> Nothing interesting or new, just merges up with the latest 2.4.1-pre1
> patch from Linus.
> 
> ftp.kernel.org:/pub/linux/kernel/people/davem/zerocopy-2.4.1p1-1.diff.gz
> 
> I haven't had any reports from anyone, which must mean that it is
> working perfectly fine and adds no new bugs, testers are thus in
> nirvana and thus have nothing to report.  :-)

Is there any value to supporting fragments in a driver which doesn't do
hardware checksumming?  IIRC Alexey had a patch to do such for Tulip,
but I don't see it in the above patchset.

	Jeff


-- 
Jeff Garzik       | "You see, in this world there's two kinds of
Building 1024     |  people, my friend: Those with loaded guns
MandrakeSoft      |  and those who dig. You dig."  --Blondie
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-10  1:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-10  0:55 Updated zerocopy patch up on kernel.org David S. Miller
2001-01-10  1:23 ` Jeff Garzik [this message]
2001-01-10  1:20   ` David S. Miller
2001-01-11 10:41     ` Ingo Molnar
2001-01-11  4:33       ` David S. Miller
2001-01-11 10:38 ` Ingo Molnar
2001-01-11 12:47   ` Andrew Morton
2001-01-13  6:46   ` Anton Blanchard

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=3A5BB985.8A249BE1@mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    /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