From: Jeff Kirsher <jeffrey.t.kirsher@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH 2/2] i40e: Disable Check for Hang
Date: Fri, 25 Sep 2015 16:16:33 -0700 [thread overview]
Message-ID: <1443222993.2987.45.camel@intel.com> (raw)
In-Reply-To: <1443207609-171288-2-git-send-email-anjali.singhai@intel.com>
On Fri, 2015-09-25 at 12:00 -0700, Anjali Singhai Jain wrote:
> The driver doesn't need its own check for hang logic as there are no
> known issues that cause HW Tx Hangs. This logic was actually
> (mis)firing frequently, causing us to reset when we didn't need to.
> If a true tx hang happens, just wait for the stack logic to catch the
> issue and send us a tx_timeout.
>
> Signed-off-by: Anjali Singhai Jain <anjali.singhai@intel.com>
> ---
> drivers/net/ethernet/intel/i40e/i40e_main.c | 99 +------------------
> ----------
> drivers/net/ethernet/intel/i40e/i40e_txrx.c | 70 -------------------
> -
> drivers/net/ethernet/intel/i40e/i40e_txrx.h | 8 ---
> 3 files changed, 1 insertion(+), 176 deletions(-)
Does not apply at all to my next-queue tree, dev-queue branch.
Dropping this patch.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20150925/82234a5d/attachment.asc>
next prev parent reply other threads:[~2015-09-25 23:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 19:00 [Intel-wired-lan] [PATCH 1/2] i40e: Fix RS bit update in Tx path and disable force WB workaround Anjali Singhai Jain
2015-09-25 19:00 ` [Intel-wired-lan] [PATCH 2/2] i40e: Disable Check for Hang Anjali Singhai Jain
2015-09-25 23:16 ` Jeff Kirsher [this message]
2015-09-25 19:50 ` [Intel-wired-lan] [PATCH 1/2] i40e: Fix RS bit update in Tx path and disable force WB workaround Singhai, Anjali
2015-09-25 23:18 ` Jeff Kirsher
2015-09-26 0:00 ` Singhai, Anjali
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=1443222993.2987.45.camel@intel.com \
--to=jeffrey.t.kirsher@intel.com \
--cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.