netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: jeffrey.t.kirsher@intel.com
Cc: netdev@vger.kernel.org, gospo@redhat.com, alexander.h.duyck@intel.com
Subject: Re: [net-2.6 PATCH 4/4] igb: check both function bits in status register in wol exception
Date: Wed, 23 Dec 2009 20:55:49 -0800 (PST)	[thread overview]
Message-ID: <20091223.205549.242128476.davem@davemloft.net> (raw)
In-Reply-To: <20091223232145.16146.15465.stgit@localhost.localdomain>

From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Date: Wed, 23 Dec 2009 15:21:46 -0800

> From: Alexander Duyck <alexander.h.duyck@intel.com>
> 
> The ethtool code for enabling Wake on Lan was not correctly checking the
> status register bits so as a result ports 0 and 2 were both being allowed
> to set WOL to enabled even though it is only supported on the first port
> for our adapters.
> 
> Signed-off-by: Alexander Duyck <alexander.h.duyck@intel.com>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>

Applied.

  reply	other threads:[~2009-12-24  4:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-23 23:20 [net-2.6 PATCH 1/4] igb: do not force pcs link when in KX mode Jeff Kirsher
2009-12-23 23:21 ` [net-2.6 PATCH 2/4] igb: do not force retry count to 1 on 82580 phy Jeff Kirsher
2009-12-24  4:55   ` David Miller
2009-12-23 23:21 ` [net-2.6 PATCH 3/4] igb: correctly offset 82575 flow control watermarks by 16 bytes Jeff Kirsher
2009-12-24  4:55   ` David Miller
2009-12-23 23:21 ` [net-2.6 PATCH 4/4] igb: check both function bits in status register in wol exception Jeff Kirsher
2009-12-24  4:55   ` David Miller [this message]
2009-12-24  4:55 ` [net-2.6 PATCH 1/4] igb: do not force pcs link when in KX mode David Miller

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=20091223.205549.242128476.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=alexander.h.duyck@intel.com \
    --cc=gospo@redhat.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;
as well as URLs for NNTP newsgroup(s).