From: "Nemeth, Balazs" <balazs.nemeth@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] ixgbe: fix link speed detection of ixgbevf
Date: Thu, 18 Dec 2014 19:57:56 +0000 [thread overview]
Message-ID: <20141218195756.GA14381@bn-ivy12> (raw)
This patch is actually a workaround to the problem. By setting
get_link_status just before calling ixgbe_check_link defeats the whole
purpose of the variable and results in _always_ getting the link
status. I think that this patch should be superseded by the following
patch:
http://dpdk.org/dev/patchwork/patch/2104/
reply other threads:[~2014-12-18 19:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20141218195756.GA14381@bn-ivy12 \
--to=balazs.nemeth@intel.com \
--cc=1415538088-11249-1-git-send-email-choonho.son@gmail.com \
--cc=dev@dpdk.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).