From: Andi Kleen <andi@firstfloor.org>
To: "Eliezer Tamir" <eliezert@broadcom.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"jeff@garzik.org" <jeff@garzik.org>,
"Michael Chan" <mchan@broadcom.com>
Subject: Re: [PATCH][BNX2X] round three
Date: Fri, 12 Oct 2007 16:47:28 +0200 [thread overview]
Message-ID: <p73641c4cfz.fsf@bingen.suse.de> (raw)
In-Reply-To: <1192038559.29746.127.camel@eliezer> (Eliezer Tamir's message of "Wed\, 10 Oct 2007 19\:49\:19 +0200")
"Eliezer Tamir" <eliezert@broadcom.com> writes:
> * For now depend on x86 or x86_64, will add more architectures ASAP.
Why is that? Linux drivers normally should not be architecture specific.
-Andi
next prev parent reply other threads:[~2007-10-12 14:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-10 17:49 [PATCH][BNX2X] round three Eliezer Tamir
2007-10-10 19:52 ` Eliezer Tamir
2007-10-11 0:59 ` David Miller
2007-10-11 17:53 ` Eliezer Tamir
2007-10-11 21:40 ` David Miller
2007-10-11 1:28 ` Stephen Hemminger
2007-10-11 17:13 ` Eliezer Tamir
2007-10-11 1:54 ` [PATCH][BNX2X] round three - sparse warnings Stephen Hemminger
2007-10-11 17:21 ` Eliezer Tamir
2007-10-12 14:47 ` Andi Kleen [this message]
2007-10-12 22:03 ` [PATCH][BNX2X] round three David Miller
2007-10-15 15:27 ` Eliezer Tamir
2007-10-15 16:05 ` Andi Kleen
2007-10-15 16:22 ` Eliezer Tamir
2007-10-15 16:24 ` Andi Kleen
2007-10-15 19:42 ` David Miller
2007-10-15 19:38 ` David Miller
2007-10-15 21:58 ` Stephen Hemminger
2007-10-15 22:00 ` David Miller
2007-10-15 22:06 ` Stephen Hemminger
2007-10-16 15:00 ` Eliezer Tamir
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=p73641c4cfz.fsf@bingen.suse.de \
--to=andi@firstfloor.org \
--cc=davem@davemloft.net \
--cc=eliezert@broadcom.com \
--cc=jeff@garzik.org \
--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 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.