netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chris Snook <csnook@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: netdev@vger.kernel.org, atl2-test@lists.sourceforge.net,
	jcliburn@gmail.com
Subject: Re: [PATCH 0/4] atlx: add atl2 support
Date: Sun, 14 Sep 2008 23:26:53 -0400	[thread overview]
Message-ID: <48CDD5FD.1040503@redhat.com> (raw)
In-Reply-To: <20080915032102.GB3028@havoc.gtf.org>

Jeff Garzik wrote:
> On Sun, Sep 14, 2008 at 06:14:10PM -0400, Chris Snook wrote:
>> Jeff Garzik wrote:
>>> Chris Snook wrote:
>>>> This patchset adds support for atl2 hardware to the atlx codebase.  It is
>>>> functionally very similar to the out-of-tree 2.0.4 version that many  
>>>> distros
>>>> have been shipping for a few months, though it adds a fix from 
>>>> Atheros to fix
>>>> the problem of device resets under heavy bidirectional load.
>>>>
>>>> The code needs a lot of janitorial work, and there's a lot of  
>>>> low-hanging fruit
>>>> for merging similar atl1 code into the shared atlx code, but I think  
>>>> that work
>>>> will go much faster once this is in-tree.  The driver is known to 
>>>> work well for
>>>> laptop and desktop use.  The only major bugs are device 
>>>> initialization problems
>>>> that manifest themselves immediately and obviously (the NIC doesn't  
>>>> work) with
>>>> certain motherboards.
>>>>
>>>> Please consider this for the 2.6.28 merge window.
>>>>
>>>> -- Chris
>>>>
>>>>  drivers/net/Kconfig       |   17
>>>>  drivers/net/Makefile      |    1
>>>>  drivers/net/atlx/Makefile |    1
>>>>  drivers/net/atlx/atl2.c   | 3101  
>>>> ++++++++++++++++++++++++++++++++++++++++++++++
>>>>  drivers/net/atlx/atl2.h   |  482 +++++++
>>>>  include/linux/pci_ids.h   |    1
>>>>  6 files changed, 3600 insertions(+), 3 deletions(-)
>>> Send as one big patch, please?
>>>
>>>
>> It's too big for vger as one patch.  There's a lot of code that can be 
>> whittled down, but this driver has been delayed for months already 
>> waiting for that to be finished.  Would you prefer a gzipped One Big 
>> Patch?
> 
> _I_ need it in standard patch format, as one big patch.  No MIME
> encoding, no gzip, no URLs, just a patch like any other.
> 
> 	Jeff

See Jay's post, in single-patch form, with some additional cosmetic cleanups and 
my signoff.

-- Chris

      reply	other threads:[~2008-09-15  3:30 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09  6:12 [PATCH 0/4] atlx: add atl2 support Chris Snook
2008-09-09  6:15 ` [PATCH 1/4] atlx: add atl2 pci id Chris Snook
2008-09-09  6:19 ` [PATCH 2/4] atlx: add atl2.h Chris Snook
2008-09-10  1:43   ` Jay Cliburn
2008-09-10  2:12     ` Chris Snook
2008-09-09  6:22 ` [PATCH 3/4] atlx: add atl2.c Chris Snook
2008-09-10  1:44   ` Jay Cliburn
2008-09-10  2:16     ` Chris Snook
2008-09-09  6:24 ` [PATCH 4/4] atlx: update build files for atl2 Chris Snook
2008-09-10  1:47   ` Jay Cliburn
2008-09-10  2:24     ` Chris Snook
2008-09-09  6:32 ` [PATCH 0/4] atlx: add atl2 support Chris Snook
2008-09-10  1:49 ` Jay Cliburn
2008-09-10  1:58 ` Jay Cliburn
2008-09-13 19:40 ` Jeff Garzik
2008-09-14 22:14   ` Chris Snook
2008-09-15  3:21     ` Jeff Garzik
2008-09-15  3:26       ` Chris Snook [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=48CDD5FD.1040503@redhat.com \
    --to=csnook@redhat.com \
    --cc=atl2-test@lists.sourceforge.net \
    --cc=jcliburn@gmail.com \
    --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 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).