netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Michael Chan <mchan@broadcom.com>
Cc: davem@davemloft.net, jgarzik@redhat.com, netdev@oss.sgi.com,
	ffan@broadcom.com, lusinsky@broadcom.com
Subject: Re: A new driver for Broadcom bcm5706
Date: Fri, 27 May 2005 08:41:15 +0100	[thread overview]
Message-ID: <20050527074115.GA28208@infradead.org> (raw)
In-Reply-To: <1116609329.31523.16.camel@rh4>

On Fri, May 20, 2005 at 10:15:29AM -0700, Michael Chan wrote:
> A new driver bnx2 for Broadcom bcm5706 is available. Since the patch is
> over 500K, I've put it on the ftp server:
> 
> ftp://Net_sys_anon@ftp1.broadcom.com/bnx2-2.patch
> 
> The patch also includes new 1000BASE-X advertisement bit definitions in
> mii.h

These defintions overlap older 10MB/s defintions.  I don't think the number
space is scare enough to need this hack.  If we absolutely want to keep it
you should at least add some big comments explaining it.

  parent reply	other threads:[~2005-05-27  7:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-20 17:15 A new driver for Broadcom bcm5706 Michael Chan
2005-05-20 19:42 ` Jeff Garzik
2005-05-20 20:51   ` Jeff Garzik
2005-05-20 21:07     ` Ben Greear
2005-05-20 21:09       ` Jeff Garzik
2005-05-20 20:17         ` Michael Chan
2005-05-20 21:58           ` Ben Greear
2005-05-20 22:28   ` David S. Miller
2005-05-20 23:04     ` Michael Chan
2005-05-21  4:35       ` David S. Miller
2005-05-21  4:36       ` David S. Miller
2005-05-20 23:30     ` Jeff Garzik
2005-05-20 23:45       ` David S. Miller
2005-05-21  0:01         ` Jeff Garzik
2005-05-20 23:11           ` Michael Chan
2005-05-21  4:28           ` David S. Miller
2005-05-20 21:18 ` Jeff Garzik
2005-05-27  7:41 ` Christoph Hellwig [this message]
2005-05-27 15:58   ` Michael Chan
2005-05-27 17:15     ` Christoph Hellwig

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=20050527074115.GA28208@infradead.org \
    --to=hch@infradead.org \
    --cc=davem@davemloft.net \
    --cc=ffan@broadcom.com \
    --cc=jgarzik@redhat.com \
    --cc=lusinsky@broadcom.com \
    --cc=mchan@broadcom.com \
    --cc=netdev@oss.sgi.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).