From: Olaf Hering <olh@suse.de>
To: "Venkatesan, Ganesh" <ganesh.venkatesan@intel.com>
Cc: netdev@oss.sgi.com, "Ronciak, John" <john.ronciak@intel.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
linuxppc64-dev@ozlabs.org
Subject: Re: [PATCH] e1000, errata 2{3, 4} - possible EEH or memory corruption when DMA crosses a 64k boundary
Date: Tue, 1 Feb 2005 20:40:10 +0100 [thread overview]
Message-ID: <20050201194010.GA7892@suse.de> (raw)
In-Reply-To: <468F3FDA28AA87429AD807992E22D07E041A065B@orsmsx408>
On Tue, Feb 01, Venkatesan, Ganesh wrote:
> In any case, this fix is required in e1000. It is *not* in the latest
> driver that is released but *is* in the driver that is lined up for
> release in a couple of weeks.
Thats good enough, just that things dont get lost. There are probably a
few separate patches for each problem found.
We are still in the process of sorting out our +2k patch mess.
next prev parent reply other threads:[~2005-02-01 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-01 19:36 [PATCH] e1000, errata 2{3, 4} - possible EEH or memory corruption when DMA crosses a 64k boundary Venkatesan, Ganesh
2005-02-01 19:40 ` Olaf Hering [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-01 19:27 Olaf Hering
2005-02-01 19:33 ` Jon Mason
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=20050201194010.GA7892@suse.de \
--to=olh@suse.de \
--cc=ganesh.venkatesan@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=linuxppc64-dev@ozlabs.org \
--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.