All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Stonehouse <rstonehouse@solarflare.com>
To: netdev@vger.kernel.org
Cc: linux-net-drivers@solarflare.com, spope@solarflare.com
Subject: [PATCH]  New driver "sfc" for Solarstorm SFC4000 controller - 3nd try
Date: Fri, 21 Dec 2007 16:53:40 +0000	[thread overview]
Message-ID: <476BEF94.4000801@solarflare.com> (raw)

This is a resubmission of a new driver for Solarflare network controllers.

The driver supports several types of PHY (10Gbase-T, XFP, CX4) on six
different 10G and 1G boards.

The previous thread was:
  [PATCH] [RFC] New driver "sfc" for Solarstorm SFC4000 controller
  http://marc.info/?l=linux-netdev&m=119757352830103&w=2

Thanks to the people who looked at the previous patches. We have addressed
the following from received comments after the 2nd submission:
  - Use kzalloc where appropriate
  - Remove deprecated fastcall attributes
  - Use kernel routines for hex dumps and MAC address printing
  - Changes to logging MACROs

The last two patches were marked with RFC but I now think that this driver
is ready (withstanding any further review comments) and I would like to ask
that this driver is considered for merging.


The patch (against net-2.6.25) is at:
     https://support.solarflare.com/netdev/3/net-2.6.25-sfc-2.2.0029.patch

The new files may also be downloaded as a tarball:
     https://support.solarflare.com/netdev/3/net-2.6.25-sfc-2.2.0029.tgz

And for verification there is:
     https://support.solarflare.com/netdev/3/MD5SUMS


Happy Christmas

-- 
Robert Stonehouse

             reply	other threads:[~2007-12-21 16:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-21 16:53 Robert Stonehouse [this message]
2007-12-21 18:02 ` [PATCH] New driver "sfc" for Solarstorm SFC4000 controller - 3nd try Randy Dunlap
2007-12-21 18:30   ` Ben Hutchings

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=476BEF94.4000801@solarflare.com \
    --to=rstonehouse@solarflare.com \
    --cc=linux-net-drivers@solarflare.com \
    --cc=netdev@vger.kernel.org \
    --cc=spope@solarflare.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 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.