From: Jeff Garzik <jgarzik@pobox.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: linux-net@vger.kernel.org, Netdev <netdev@oss.sgi.com>
Subject: Re: Seventh release of i82586 drivers: Novell NE3200, Microdyne EXOS 205T/215T and Intel EtherExpress 16
Date: Sat, 24 Jan 2004 20:09:48 -0500 [thread overview]
Message-ID: <4013175C.6090607@pobox.com> (raw)
In-Reply-To: <20031107192543.A1921@sygehus.dk>
Rask Ingemann Lambertsen wrote:
> I now have patches against linux 2.4.22-bk45. Due to the size I won't post
> them to the list. They can be downloaded instead:
>
> <URL:http://users.cybercity.dk/~ccc94453/linux/i82586/i82586-2.4.22bk45.patch1.bz2>
> (bzip2 compressed, 41140 bytes)
> <URL:http://users.cybercity.dk/~ccc94453/linux/i82586/i82586-2.4.22bk45.patch1.txt>
> (uncompressed, 175346 bytes)
I've been slow getting to these... any chance you could re-diff against
2.4.25-pre7?
> Btw, if/when I make more updates, should I make full patches or
> incremental patches?
Up to you. In general, I prefer being "mailbombed" with multiple
patches, against the latest kernel or latest netdev.
Jeff
P.S. I haven't forgotten about your de2104x mtu patch either, need to
review that soon.
next parent reply other threads:[~2004-01-25 1:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031031155341.B1773@sygehus.dk>
[not found] ` <3FA2854C.9080801@pobox.com>
[not found] ` <20031031180525.A1984@sygehus.dk>
[not found] ` <20031107192543.A1921@sygehus.dk>
2004-01-25 1:09 ` Jeff Garzik [this message]
2004-02-05 19:45 ` Seventh release of i82586 drivers: Novell NE3200, Microdyne EXOS 205T/215T and Intel EtherExpress 16 Rask Ingemann Lambertsen
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=4013175C.6090607@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-net@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=rask@sygehus.dk \
/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).