From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: shemminger@vyatta.com, dcbw@redhat.com, netdev@vger.kernel.org,
linux-net-drivers@solarflare.com
Subject: Re: [PATCH] New driver "sfc" for Solarstorm SFC4000 controller (try #7)
Date: Wed, 5 Mar 2008 14:22:04 +0000 [thread overview]
Message-ID: <20080305142203.GQ2988@solarflare.com> (raw)
In-Reply-To: <20080303.132941.176565936.davem@davemloft.net>
David,
We concede that the driver is currently too large to be properly
reviewed in one go.
We propose to:
1. Remove what we can - i.e. internal HW support, extraneous comments,
unused HW register defines, and non-essential peripheral driver features
such as sensor support - leaving a minimal network driver.
2. Post the minimal driver in sub-100K patches to netdev. This
minimal driver will still require several patches, but future patches
should represent independent pieces of functionality.
If you can see reasons why this will still not get us to a point where
a review can take place then please tell us what else is required.
We hope to complete this work within the next few days.
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
next prev parent reply other threads:[~2008-03-05 14:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 18:56 [PATCH] New driver "sfc" for Solarstorm SFC4000 controller (try #7) Ben Hutchings
2008-03-03 18:58 ` Ben Hutchings
2008-03-03 19:02 ` David Miller
2008-03-03 19:22 ` Dan Williams
2008-03-03 20:39 ` Stephen Hemminger
2008-03-03 21:17 ` Ben Hutchings
2008-03-03 21:29 ` David Miller
2008-03-05 14:22 ` Ben Hutchings [this message]
2008-03-05 18:38 ` David Miller
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=20080305142203.GQ2988@solarflare.com \
--to=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=linux-net-drivers@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).