From: "David S. Miller" <davem@davemloft.net>
To: jesse.brandeburg@gmail.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
jeff@garzik.org, cramerj@intel.com, john.ronciak@intel.com,
jesse.brandeburg@intel.com
Subject: Re: [PATCH]: e1000 endianness bugs
Date: Wed, 15 Mar 2006 15:40:46 -0800 (PST) [thread overview]
Message-ID: <20060315.154046.130190626.davem@davemloft.net> (raw)
In-Reply-To: <4807377b0603151533i6a693d99ycdab71fe0a21dc4c@mail.gmail.com>
From: "Jesse Brandeburg" <jesse.brandeburg@gmail.com>
Date: Wed, 15 Mar 2006 15:33:43 -0800
> Yep, those look like bugs to me, thanks and congratulations, you're
> the first person to test our PCI Express adapters in a big endian
> system (they haven't been available before, and we don't have one,
> yet)
It was onboard a Niagara T2000 system.
next prev parent reply other threads:[~2006-03-15 23:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 22:26 [PATCH]: e1000 endianness bugs David S. Miller
2006-03-15 23:33 ` Jesse Brandeburg
2006-03-15 23:40 ` David S. Miller [this message]
2006-03-16 7:31 ` Christoph Hellwig
2006-03-17 0:17 ` Jeff Garzik
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=20060315.154046.130190626.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=cramerj@intel.com \
--cc=jeff@garzik.org \
--cc=jesse.brandeburg@gmail.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linux-kernel@vger.kernel.org \
--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).