From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Jeff Garzk <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/6] sky2: version 1.18 (rev2)
Date: Wed, 19 Sep 2007 15:36:41 -0700 [thread overview]
Message-ID: <20070919223641.860189786@linux-foundation.org> (raw)
Patches against 2.6.23 to fix bugs and support newest FE+
chip. These patches conflict with those in netdev-2.6
upstream branch, Jeff how do you want to resolve that?
--
Stephen Hemminger <shemminger@linux-foundation.org>
next reply other threads:[~2007-09-19 23:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-19 22:36 Stephen Hemminger [this message]
2007-09-19 22:36 ` [PATCH 1/6] sky2: fix VLAN receive processing (resend) Stephen Hemminger
2007-09-20 3:47 ` Jeff Garzik
2007-09-19 22:36 ` [PATCH 2/6] sky2: ethtool speed report bug Stephen Hemminger
2007-09-19 22:36 ` [PATCH 3/6] sky2: reorganize chip revision features Stephen Hemminger
2007-09-19 23:27 ` Rick Jones
2007-09-19 22:36 ` [PATCH 4/6] sky2: fe+ chip support Stephen Hemminger
2007-09-19 22:36 ` [PATCH 5/6] sky2: receive FIFO checking Stephen Hemminger
2007-09-19 22:36 ` [PATCH 6/6] sky2: version 1.18 Stephen Hemminger
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=20070919223641.860189786@linux-foundation.org \
--to=shemminger@linux-foundation.org \
--cc=jgarzik@pobox.com \
--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).