From: Jeff Garzik <jeff@garzik.org>
To: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, pl@us.ibm.com
Subject: Re: [PATCH 3/3] e1000e: fix EEH recovery during reset on PPC
Date: Fri, 27 Jun 2008 00:56:17 -0400 [thread overview]
Message-ID: <486472F1.4050900@garzik.org> (raw)
In-Reply-To: <20080625000120.16592.89100.stgit@localhost.localdomain>
Jeff Kirsher wrote:
> EEH is not recovering in a reasonable amount of time on PPC during
> e1000e_down().
>
> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
> Signed-off-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> ---
>
> drivers/net/e1000e/netdev.c | 3 ++-
> 1 files changed, 2 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/e1000e/netdev.c b/drivers/net/e1000e/netdev.c
> index ccb8ca2..0320925 100644
> --- a/drivers/net/e1000e/netdev.c
> +++ b/drivers/net/e1000e/netdev.c
> @@ -2535,7 +2535,8 @@ void e1000e_down(struct e1000_adapter *adapter)
> adapter->link_speed = 0;
> adapter->link_duplex = 0;
>
> - e1000e_reset(adapter);
> + if (!pci_channel_offline(adapter->pdev))
> + e1000e_reset(adapter);
> e1000_clean_tx_ring(adapter);
> e1000_clean_rx_ring(adapter);
IMO for this type of change, you should consider putting all these
changes into a single patch.
It's exactly the same logical change, so no need to split it up into
three patches.
next prev parent reply other threads:[~2008-06-27 4:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-25 0:00 [PATCH 1/3] ixgbe: fix EEH recovery during reset on PPC Jeff Kirsher
2008-06-25 0:01 ` [PATCH 2/3] igb: " Jeff Kirsher
2008-06-25 0:01 ` [PATCH 3/3] e1000e: " Jeff Kirsher
2008-06-27 4:56 ` Jeff Garzik [this message]
2008-06-27 5:52 ` Jeff Kirsher
2008-06-27 5:33 ` [PATCH 1/3] ixgbe: " 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=486472F1.4050900@garzik.org \
--to=jeff@garzik.org \
--cc=davem@davemloft.net \
--cc=jeffrey.t.kirsher@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pl@us.ibm.com \
/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).