DPDK patches and discussions
 help / color / mirror / Atom feed
From: Balazs Nemeth <balazs.nemeth@intel.com>
To: dev@dpdk.org, lee.roberts@hp.com
Subject: [dpdk-dev] [PATCH] ixgbe: logic change in ixgbe_check_mac_link_vf().
Date: Fri, 19 Dec 2014 11:31:27 +0100	[thread overview]
Message-ID: <hva9388c2ao0.fsf@intel.com> (raw)
In-Reply-To: <1414791289-6260-1-git-send-email-lee.roberts@hp.com>

This patch is a workaround for the issue at the level of the ixgbe
driver code. The problem can actually be fixed at the level of DPDK
instead.  Furthermore, this patch circumvents the problem by moving the
check that determines if the link status needs to be read (which always
fails because get_link_status is not set before the
ixgbe_check_mac_link_vf function is called) into a portion of the code
that is skipped in most cases. I believe that this patch should be
superseded by the following patch:

http://dpdk.org/dev/patchwork/patch/2104/

      reply	other threads:[~2014-12-19 10:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 21:34 lee.roberts
2014-12-19 10:31 ` Balazs Nemeth [this message]

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=hva9388c2ao0.fsf@intel.com \
    --to=balazs.nemeth@intel.com \
    --cc=dev@dpdk.org \
    --cc=lee.roberts@hp.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).