netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com>
To: jeff@garzik.org
Cc: e1000-devel@lists.sourceforge.net, netdev@vger.kernel.org
Subject: [PATCH 4/7] e1000e: fix flow control when using ethtool overrides
Date: Thu, 21 Feb 2008 15:10:57 -0800	[thread overview]
Message-ID: <20080221231057.5595.87736.stgit@localhost.localdomain> (raw)
In-Reply-To: <20080221231041.5595.4933.stgit@localhost.localdomain>

From: Jesse Brandeburg <jesse.brandeburg@intel.com>

Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
Signed-off-by: Auke Kok <auke-jan.h.kok@intel.com>
---

 drivers/net/e1000e/lib.c |    3 ---
 1 files changed, 0 insertions(+), 3 deletions(-)

diff --git a/drivers/net/e1000e/lib.c b/drivers/net/e1000e/lib.c
index 16f35fa..0860b5f 100644
--- a/drivers/net/e1000e/lib.c
+++ b/drivers/net/e1000e/lib.c
@@ -589,9 +589,6 @@ static s32 e1000_set_default_fc_generic(struct e1000_hw *hw)
 	s32 ret_val;
 	u16 nvm_data;
 
-	if (mac->fc != e1000_fc_default)
-		return 0;
-
 	/* Read and store word 0x0F of the EEPROM. This word contains bits
 	 * that determine the hardware's default PAUSE (flow control) mode,
 	 * a bit that determines whether the HW defaults to enabling or


  parent reply	other threads:[~2008-02-21 23:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-21 23:10 [PATCH 1/7] ixgb: add RNBC counter - no buffer count - to ethtool stats Auke Kok
2008-02-21 23:10 ` [PATCH 2/7] e1000e: 82573 can use eerd method to read eeprom Auke Kok
2008-02-21 23:10 ` [PATCH 3/7] e1000e: fix link up message to show ethX: Auke Kok
2008-02-21 23:10 ` Auke Kok [this message]
2008-02-21 23:11 ` [PATCH 5/7] e1000e: fix flow control denial of service possibility Auke Kok
2008-02-21 23:11 ` [PATCH 6/7] e1000e: fix spelling errors in comments Auke Kok
2008-02-21 23:11 ` [PATCH 7/7] e1000e: remove unused read value in ASPM disable code Auke Kok
2008-02-24  5:11   ` Jeff Garzik

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=20080221231057.5595.87736.stgit@localhost.localdomain \
    --to=auke-jan.h.kok@intel.com \
    --cc=e1000-devel@lists.sourceforge.net \
    --cc=jeff@garzik.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).