From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH 0/7] sky2 version 1.15 (88e8071) support
Date: Wed, 13 Jun 2007 13:37:16 -0700 [thread overview]
Message-ID: <20070613133716.39377e85@localhost> (raw)
In-Reply-To: <46704E03.8060307@garzik.org>
On Wed, 13 Jun 2007 16:05:23 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> Stephen Hemminger wrote:
> > These changes are to enable the Yukon Extreme (88e8071)
> > chipset. This chip is similar to earlier chip but has a different
> > set of offloading operations and some other minor quirks.
> >
> > Marvell has given me some evaluation boards with the 88e8071
> > chip set. The chip is available now, but haven't seen a systems
> > with the hardware yet. The support fot this is exprerimental
> > at this point, but haven't encountered any new problems.
>
> Just to confirm... these are all for #upstream (2.6.23), correct?
>
>
Yes, given that the hardware is not available on common platforms yet,
it should go into 2.6.23
prev parent reply other threads:[~2007-06-13 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-05 0:23 [PATCH 0/7] sky2 version 1.15 (88e8071) support Stephen Hemminger
2007-06-05 0:23 ` [PATCH 1/7] sky2: avoid reserved regions on ethtool reg dump Stephen Hemminger
2007-06-13 20:44 ` Jeff Garzik
2007-06-05 0:23 ` [PATCH 2/7] sky2: Add PCI device specfic register 4 & 5 Stephen Hemminger
2007-06-05 0:23 ` [PATCH 3/7] sky2: rename BMU register Stephen Hemminger
2007-06-05 0:23 ` [PATCH 4/7] sky2: enable clocks before probe Stephen Hemminger
2007-06-05 0:23 ` [PATCH 5/7] sky2: GPIO register Stephen Hemminger
2007-06-05 0:23 ` [PATCH 6/7] sky2: Yukon Extreme (88e8071) support Stephen Hemminger
2007-06-05 0:23 ` [PATCH 7/7] sky2: version 1.15 Stephen Hemminger
2007-06-13 20:05 ` [PATCH 0/7] sky2 version 1.15 (88e8071) support Jeff Garzik
2007-06-13 20:37 ` Stephen Hemminger [this message]
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=20070613133716.39377e85@localhost \
--to=shemminger@linux-foundation.org \
--cc=jeff@garzik.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.