Netdev List
 help / color / mirror / Atom feed
From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>,
	"Graham, David" <david.graham@intel.com>,
	"524699@bugs.debian.org" <524699@bugs.debian.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: e1000e NVM mutex contention warnings
Date: Thu, 23 Apr 2009 16:24:13 -0700	[thread overview]
Message-ID: <9929d2390904231624g5fab1231l57815c2311d07acb@mail.gmail.com> (raw)
In-Reply-To: <1240528484.3605.39.camel@deadeye.i.decadent.org.uk>

On Thu, Apr 23, 2009 at 4:14 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Thu, 2009-04-23 at 15:15 -0700, Brandeburg, Jesse wrote:
>> Ben Hutchings wrote:
>> > 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.
>>
>> Hi Ben,
>>
>> checking linus' tree and davem's current net-2.6 tree shows that the
>> code was removed as of commit: 0a834a36ac92375cd82d9e4fe4f571e257997d6a
>>
>> it was put in 2/14/2009, and was included in 2.6.30-rc1 by linus.
>
> Thanks.  I had a look but somehow missed that this was already on the
> way out in 2.6.30.
>
>> are you suggesting that we maybe try to push to -stable too?
>
> If you now have the information you need about contention, then it seems
> to me that it would be worthwhile to remove the unnecessary warnings.
> If you don't want to submit a stable update then I can patch it out in
> the Debian kernel package.
>
> Ben.

I am fine with pushing this patch to -stable.

-- 
Cheers,
Jeff

      reply	other threads:[~2009-04-23 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 13:17 e1000e NVM mutex contention warnings Ben Hutchings
2009-04-23 22:15 ` Brandeburg, Jesse
2009-04-23 23:14   ` Ben Hutchings
2009-04-23 23:24     ` Jeff Kirsher [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=9929d2390904231624g5fab1231l57815c2311d07acb@mail.gmail.com \
    --to=jeffrey.t.kirsher@intel.com \
    --cc=524699@bugs.debian.org \
    --cc=ben@decadent.org.uk \
    --cc=david.graham@intel.com \
    --cc=jesse.brandeburg@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