All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Chan" <mchan@broadcom.com>
To: "Jeff Garzik" <jgarzik@pobox.com>
Cc: "Ben Greear" <greearb@candelatech.com>,
	davem@davemloft.net, netdev@oss.sgi.com, ffan@broadcom.com,
	lusinsky@broadcom.com
Subject: Re: A new driver for Broadcom bcm5706
Date: Fri, 20 May 2005 13:17:36 -0700	[thread overview]
Message-ID: <1116620256.31523.23.camel@rh4> (raw)
In-Reply-To: <20050520210938.GA23714@havoc.gtf.org>

On Fri, 2005-05-20 at 17:09 -0400, Jeff Garzik wrote:
> On Fri, May 20, 2005 at 02:07:17PM -0700, Ben Greear wrote:
> > I dig having the chipset manufacturer
> > solidly behind the driver, like e1000!
> 
> Clearly you have been asleep :)  Broadcom has been contributing actively
> to tg3.
> 

Yes, we are solidly behind tg3 and bnx2.

  reply	other threads:[~2005-05-20 20:17 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 [this message]
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
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=1116620256.31523.23.camel@rh4 \
    --to=mchan@broadcom.com \
    --cc=davem@davemloft.net \
    --cc=ffan@broadcom.com \
    --cc=greearb@candelatech.com \
    --cc=jgarzik@pobox.com \
    --cc=lusinsky@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 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.