From: David Miller <davem@davemloft.net>
To: zach@vmware.com
Cc: jesse.brandeburg@intel.com, chrisl@vmware.com,
akpm@linux-foundation.org, arvidjaar@mail.ru,
bruce.w.allan@intel.com, jeff@garzik.org,
jeffrey.t.kirsher@intel.com, john.ronciak@intel.com,
peter.p.waskiewicz.jr@intel.com, pratap@vmware.com,
netdev@vger.kernel.org, mm-commits@vger.kernel.org
Subject: Re: + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mmtree
Date: Wed, 03 Sep 2008 01:24:32 -0700 (PDT) [thread overview]
Message-ID: <20080903.012432.75866225.davem@davemloft.net> (raw)
In-Reply-To: <1220429845.32688.182.camel@bodhitayantram.eng.vmware.com>
From: Zachary Amsden <zach@vmware.com>
Date: Wed, 03 Sep 2008 01:17:25 -0700
> Thus, the obvious answer to me is ... LOCK AROUND EEPROM READS AND
> WRITES now and figure out if there are deeper issues due to network
> layer and E1000 complexities later, but ELIMINATE THE CATASTROPHIC
> FAILURES ASAP.
I totally agree with Zach here.
The fact that we are still masterbating about this bug and a fix
isn't in the tree is absolutely rediculious.
next prev parent reply other threads:[~2008-09-03 8:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200809021919.m82JJweC008488@imap1.linux-foundation.org>
2008-09-02 21:58 ` + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mm tree 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 [this message]
2008-09-03 17:04 ` Andrey Borzenkov
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=20080903.012432.75866225.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--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=mm-commits@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=pratap@vmware.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 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).