From: Christopher Li <chrisl@vmware.com>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: Zach Amsden <zach@vmware.com>,
"Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"arvidjaar@mail.ru" <arvidjaar@mail.ru>,
"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>,
Pratap Subrahmanyam <pratap@vmware.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mm-commits@vger.kernel.org" <mm-commits@vger.kernel.org>
Subject: Re: + e1000e-prevent-corruption-of-eeprom-nvm.patch added to -mm tree
Date: Tue, 2 Sep 2008 20:04:49 -0700 [thread overview]
Message-ID: <20080903030448.GB26161@vmware.com> (raw)
In-Reply-To: <20080903004454.GV7908@solarflare.com>
On Tue, Sep 02, 2008 at 05:44:56PM -0700, Ben Hutchings wrote:
>
> All ethtool commands are serialised by the RTNL as Jesse said above.
>
What Zach trying to say is that, ioctl is not the only way to
reach the eepro read/write code inside the kernel.
Chris
prev parent reply other threads:[~2008-09-03 3:13 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
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 [this message]
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=20080903030448.GB26161@vmware.com \
--to=chrisl@vmware.com \
--cc=akpm@linux-foundation.org \
--cc=arvidjaar@mail.ru \
--cc=bhutchings@solarflare.com \
--cc=bruce.w.allan@intel.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 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.