From: David Miller <davem@davemloft.net>
To: aaron.f.brown@intel.com
Cc: michele@acksyn.org, netdev@vger.kernel.org,
e1000-devel@lists.sourceforge.net, idirectscm@aim.com
Subject: Re: [PATCH net] e100: Fix "disabling already-disabled device" warning
Date: Thu, 30 Jan 2014 16:45:38 -0800 (PST) [thread overview]
Message-ID: <20140130.164538.1074744859012249672.davem@davemloft.net> (raw)
In-Reply-To: <309B89C4C689E141A5FF6A0C5FB2118B7314C041@ORSMSX101.amr.corp.intel.com>
From: "Brown, Aaron F" <aaron.f.brown@intel.com>
Date: Fri, 31 Jan 2014 00:40:16 +0000
>> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org]
>> On Behalf Of David Miller
>> Sent: Thursday, January 30, 2014 4:28 PM
>> To: michele@acksyn.org
>> Cc: netdev@vger.kernel.org; e1000-devel@lists.sourceforge.net;
>> idirectscm@aim.com
>> Subject: Re: [PATCH net] e100: Fix "disabling already-disabled device"
>> warning
>>
>> From: Michele Baldessari <michele@acksyn.org>
>> Date: Thu, 30 Jan 2014 10:51:04 +0000
>>
>> > In https://bugzilla.redhat.com/show_bug.cgi?id=994438 and
>> > https://bugzilla.redhat.com/show_bug.cgi?id=970480 we received
>> > different reports of e100 throwing the following
>> > warning:
>> ...
>> > This patch removes pci_disable_device() from __e100_shutdown().
>> > pci_clear_master() is enough.
>> >
>> > Signed-off-by: Michele Baldessari <michele@acksyn.org>
>> > Tested-by: Mark Harig <idirectscm@aim.com>
>
> Signed-off-by: Aaron Brown <aaron.f.brown@intel.com>
>
> Sorry if it's a duplicate, one I sent out earlier did not seem to hit netdev.
I think this patch was posted twice, once without netdev properly
CC:'d and you replied to that copy.
Thanks Aaron, I'll apply this.
prev parent reply other threads:[~2014-01-31 0:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 10:51 [PATCH net] e100: Fix "disabling already-disabled device" warning Michele Baldessari
2014-01-30 20:17 ` Brown, Aaron F
2014-01-31 0:27 ` David Miller
2014-01-31 0:40 ` Brown, Aaron F
2014-01-31 0:45 ` David Miller [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=20140130.164538.1074744859012249672.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=aaron.f.brown@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=idirectscm@aim.com \
--cc=michele@acksyn.org \
--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;
as well as URLs for NNTP newsgroup(s).