From: Andrey Borzenkov <arvidjaar@mail.ru>
To: Zachary Amsden <zach@vmware.com>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
Qicheng Christopher Li <chrisl@vmware.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"jeff@garzik.org" <jeff@garzik.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mmtree
Date: Wed, 3 Sep 2008 21:04:47 +0400 [thread overview]
Message-ID: <200809032104.49092.arvidjaar@mail.ru> (raw)
In-Reply-To: <1220429845.32688.182.camel@bodhitayantram.eng.vmware.com>
[-- Attachment #1: Type: text/plain, Size: 305 bytes --]
On Wednesday 03 September 2008, Zachary Amsden wrote:
> I'm sorry, we have no way to reproduce this, don't know anything about
> the hardware the customer was using
According to my information bug affects LAN controllers based on Intel 8254x GBe chipset. Of course, I do not claim it is exhaustive list.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-03 18:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 19:19 + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mm tree akpm
2008-09-02 21:58 ` Brandeburg, Jesse
2008-09-02 23:31 ` Zachary Amsden
2008-09-03 0:32 ` + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mmtree Brandeburg, Jesse
2008-09-03 2:48 ` Christopher Li
2008-09-03 8:17 ` Zachary Amsden
2008-09-03 8:24 ` David Miller
2008-09-03 17:04 ` Andrey Borzenkov [this message]
2008-09-09 2:20 ` Allan, Bruce W
2008-09-03 0:44 ` + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mm tree Ben Hutchings
2008-09-03 3:04 ` Christopher Li
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=200809032104.49092.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=akpm@linux-foundation.org \
--cc=bruce.w.allan@intel.com \
--cc=chrisl@vmware.com \
--cc=jeff@garzik.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=zach@vmware.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.