From: Jeff Garzik <jgarzik@pobox.com>
To: Manfred Spraul <manfred@colorfullife.com>
Cc: marcelo.tosatti@cyclades.com, blazara@nvidia.com, netdev@oss.sgi.com
Subject: Re: [PATCH 2.4.28-rc1-bk3] forcedeth: Backport of gigabit ethernet support and media detection rewrite
Date: Sat, 30 Oct 2004 09:00:11 -0400 [thread overview]
Message-ID: <20041030130011.GA4261@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0410301442220.25784-100000@dbl.q-ag.de>
On Sat, Oct 30, 2004 at 02:53:08PM +0200, Manfred Spraul wrote:
> Differences between 2.6 and 2.4:
>
> - static msleep helper added.
Sigh, libata has this too. I'll work up a patch to make it public.
> After applying this patch, the driver is nearly in sync with 2.6.10-rc1:
> The only additional differences are __iomem annotations and the use of
> netdev_priv.
Will __iomem and netdev_priv() changes be in a separate patch?
2.4.x has both.
Jeff
next prev parent reply other threads:[~2004-10-30 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-30 12:53 [PATCH 2.4.28-rc1-bk3] forcedeth: Backport of gigabit ethernet support and media detection rewrite Manfred Spraul
2004-10-30 13:00 ` Jeff Garzik [this message]
2004-10-30 13:09 ` Manfred Spraul
2004-10-30 14:13 ` Jeff Garzik
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=20041030130011.GA4261@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=blazara@nvidia.com \
--cc=manfred@colorfullife.com \
--cc=marcelo.tosatti@cyclades.com \
--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;
as well as URLs for NNTP newsgroup(s).