From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: Balazs Nemeth <balazs.nemeth-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH] ixgbe_vf: Fix getting link state
Date: Wed, 17 Dec 2014 14:24:36 +0100 [thread overview]
Message-ID: <2180089.WsPSvRpvUk@xps13> (raw)
In-Reply-To: <1418822554-1493-1-git-send-email-balazs.nemeth-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-17 13:22, Balazs Nemeth:
> This patch fixes checking the link state of a virtual function. If the
> state has already been checked, it does not need to be checked
> again. Previously, get_link_status in the ixgbe_hw struct was
> used to track if the information had already been updated, but this
> field was always set to false.
>
> Signed-off-by: Balazs Nemeth <balazs.nemeth-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
This is the third patch about link status fix in ixgbevf.
Please comment the other ones in the respective mailing threads:
http://dpdk.org/dev/patchwork/patch/1079
http://dpdk.org/dev/patchwork/patch/1224
Are they superseded by yours?
--
Thomas
next prev parent reply other threads:[~2014-12-17 13:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 13:22 [PATCH] ixgbe_vf: Fix getting link state Balazs Nemeth
[not found] ` <1418822554-1493-1-git-send-email-balazs.nemeth-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-17 13:24 ` Thomas Monjalon [this message]
2014-12-18 4:20 ` Choonho Son
2014-12-18 17:56 ` [PATCH v2] " Balazs Nemeth
[not found] ` <1418925396-14206-1-git-send-email-balazs.nemeth-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-12-19 15:34 ` Gonzalez Monroy, Sergio
[not found] ` <91383E96CE459D47BCE92EFBF5CE73B004F1CDCC-kPTMFJFq+rEMvF1YICWikbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-12-19 22:42 ` Thomas Monjalon
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=2180089.WsPSvRpvUk@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=balazs.nemeth-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).