netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Mike McCormack <mikem@ring3k.org>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] sky2: Serialize access to PCI config space
Date: Mon, 10 Aug 2009 08:23:15 -0700	[thread overview]
Message-ID: <20090810082315.16b7a0b9@nehalam> (raw)
In-Reply-To: <4A7EB4EF.3030106@ring3k.org>

On Sun, 09 Aug 2009 20:37:19 +0900
Mike McCormack <mikem@ring3k.org> wrote:

> 
> Disable NAPI when powering up or down the phy, as sky2_err_intr
>  may also access the PCI config space.

Maybe, but any sky2_err interrupt is a serious condition that
means hardware is being used incorrectly or dead.

  reply	other threads:[~2009-08-10 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-09 11:37 [PATCH] sky2: Serialize access to PCI config space Mike McCormack
2009-08-10 15:23 ` Stephen Hemminger [this message]
2009-08-10 15:27 ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2009-08-06 11:10 Mike McCormack
2009-08-06 15:34 ` Stephen Hemminger

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=20090810082315.16b7a0b9@nehalam \
    --to=shemminger@linux-foundation.org \
    --cc=mikem@ring3k.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).