From: "Eliezer Tamir" <eliezert@broadcom.com>
To: "Max Asbock" <masbock@us.ibm.com>
Cc: davem@davemloft.net, "Michael Chan" <mchan@broadcom.com>,
jeff@garzik.org, netdev@vger.kernel.org
Subject: Re: [RFC][BNX2X] .h files rewrite
Date: Sun, 04 Nov 2007 09:47:48 +0200 [thread overview]
Message-ID: <1194162468.4836.186.camel@eliezer> (raw)
In-Reply-To: <1194046554.6369.20.camel@w-amax.beaverton.ibm.com>
On Fri, 2007-11-02 at 16:35 -0700, Max Asbock wrote:
> I built the newest bnx2x code against the net-2.6 kernel and ran a
> number of stress tests with netperf and pktgen. I did not encounter
> any
> errors.
>
> Max
>
>
Thanks,
Eliezer
next prev parent reply other threads:[~2007-11-04 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-28 20:17 [RFC][BNX2X] .h files rewrite Eliezer Tamir
[not found] ` <1193602875.4836.28.camel@eliezer>
2007-10-29 8:39 ` David Miller
2007-10-31 10:14 ` Eliezer Tamir
2007-10-31 10:53 ` David Miller
2007-11-02 23:35 ` Max Asbock
2007-11-04 7:47 ` Eliezer Tamir [this message]
2007-11-12 23:13 ` Ram Pai
2007-11-12 23:13 ` 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=1194162468.4836.186.camel@eliezer \
--to=eliezert@broadcom.com \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=masbock@us.ibm.com \
--cc=mchan@broadcom.com \
--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).