From: Ben Hutchings <ben@decadent.org.uk>
To: David Graham <david.graham@intel.com>
Cc: Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
524699@bugs.debian.org, netdev@vger.kernel.org
Subject: e1000e NVM mutex contention warnings
Date: Sun, 19 Apr 2009 14:17:04 +0100 [thread overview]
Message-ID: <1240147024.3384.20.camel@deadeye.i.decadent.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 256 bytes --]
David,
What's your plan for collecting information about NVM mutex contention
and when do you intend to remove the warnings? I have to say I find
this way of testing very user-unfriendly and would like to see it gone
as soon as possible.
Ben.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2009-04-19 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 13:17 Ben Hutchings [this message]
2009-04-23 22:15 ` e1000e NVM mutex contention warnings Brandeburg, Jesse
2009-04-23 23:14 ` Ben Hutchings
2009-04-23 23:24 ` Jeff Kirsher
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=1240147024.3384.20.camel@deadeye.i.decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=524699@bugs.debian.org \
--cc=david.graham@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--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