linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Pekka Pietikainen <pp@netppl.fi>
Cc: Bas Mevissen <bas@basmevissen.nl>,
	torvalds@transmeta.com, alan@lxorguk.ukuu.org.uk,
	linux-kernel@vger.kernel.org
Subject: Re: REQ: BCM4400 network driver for 2.4.22
Date: Fri, 11 Jul 2003 12:58:58 -0400	[thread overview]
Message-ID: <20030711165858.GG2210@gtf.org> (raw)
In-Reply-To: <20030711163345.GA23076@netppl.fi>

On Fri, Jul 11, 2003 at 07:33:45PM +0300, Pekka Pietikainen wrote:
> On Wed, Jul 09, 2003 at 06:05:08PM -0400, Jeff Garzik wrote:
> > b44 in 2.5 supports this, and it will be backported to 2.4.
> > 
> > Pekka Pietikainen just identified several bugs, so those will get fixed 
> > in the next day or so, then b44 will be sent to Marcelo.
> Hi
> 
> Here's a patch against the driver version in 2.5.73 for testing/comments,
> which fixes all the issues I know of in the driver. I'm writing this mail
> through the driver running on 2.4.x, so obviously at least basic 
> functionality is working.
> 
> I'm not too sure about the pointer tricks I do with skb->data
> in b44_rx(), but they seem to do the trick just fine ;)

You rule, dude.  I'll give it a test here, too.

I've already merged a couple of your fixes locally, I'll suck the rest
of this patch into my queue ASAP.

If others could test this, that is much appreciated too.

	Jeff




  reply	other threads:[~2003-07-11 16:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 21:34 REQ: BCM4400 network driver for 2.4.22 Bas Mevissen
2003-07-09 22:05 ` Jeff Garzik
2003-07-11 16:33   ` Pekka Pietikainen
2003-07-11 16:58     ` Jeff Garzik [this message]
2003-07-11 20:04     ` Pekka Pietikainen
2003-07-12  3:24     ` David S. Miller
2003-07-14 20:12       ` Pekka Pietikainen

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=20030711165858.GG2210@gtf.org \
    --to=jgarzik@pobox.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=bas@basmevissen.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pp@netppl.fi \
    --cc=torvalds@transmeta.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).