From: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
To: "Cui, LunyuanX" <lunyuanx.cui@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH v3] net/e1000: fix link status update
Date: Tue, 19 Nov 2019 06:43:01 +0000 [thread overview]
Message-ID: <6A0DE07E22DDAD4C9103DF62FEBC0909408A15C5@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20191118145801.78186-1-lunyuanx.cui@intel.com>
Hi Lunyuan,
> -----Original Message-----
> From: Cui, LunyuanX
> Sent: Monday, November 18, 2019 10:58 PM
> To: dev@dpdk.org
> Cc: Lu, Wenzhuo <wenzhuo.lu@intel.com>; Cui, LunyuanX
> <lunyuanx.cui@intel.com>; stable@dpdk.org
> Subject: [PATCH v3] net/e1000: fix link status update
>
> Unassigned variable should not be used as judgment, and there is no need
Don't understand "Unassigned variable should not be used as judgment ". Which one is this " Unassigned variable"?
> to update link status according to old link status.
Don't understand why " no need to update link status according to old link status ".
Please add more info about what problem this patch wants to fix. Thanks.
> This patch fix the issue.
>
> Change the variable from link_check to link_up.
>
> Fixes: 80ba61115e77 ("net/e1000: use link status helper functions")
> Cc: stable@dpdk.org
>
> Signed-off-by: Lunyuan Cui <lunyuanx.cui@intel.com>
> ---
> v3:
> * Change the variable from link_check to link_up.
>
> v2
> * Delete incorrect judgment
> ---
> drivers/net/e1000/em_ethdev.c | 16 ++++++++--------
> 1 file changed, 8 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/net/e1000/em_ethdev.c
> b/drivers/net/e1000/em_ethdev.c index 9a88b50b2..080cbe2df 100644
> --- a/drivers/net/e1000/em_ethdev.c
> +++ b/drivers/net/e1000/em_ethdev.c
>
> /* Now we check if a transition has happened */
Looks like this comment need to be removed if the below check changes. But still, don't know why we should change the check.
> - if (link_check && (link.link_status == ETH_LINK_DOWN)) {
> + if (link_up) {
next prev parent reply other threads:[~2019-11-19 6:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 17:32 [dpdk-stable] [PATCH] " Cui LunyuanX
2019-11-14 6:41 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-11-15 14:48 ` [dpdk-stable] [PATCH v2] " Lunyuan Cui
2019-11-18 3:06 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-11-18 3:21 ` Cui, LunyuanX
2019-11-18 3:28 ` Ye Xiaolong
2019-11-18 14:58 ` [dpdk-stable] [PATCH v3] " Lunyuan Cui
2019-11-18 7:23 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-11-19 6:43 ` Lu, Wenzhuo [this message]
2019-11-20 9:22 ` [dpdk-stable] [PATCH v4] " Lunyuan Cui
2019-11-26 2:24 ` [dpdk-stable] [dpdk-dev] " Ye Xiaolong
2019-11-26 2:04 ` [dpdk-stable] [PATCH] " Lu, Wenzhuo
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=6A0DE07E22DDAD4C9103DF62FEBC0909408A15C5@shsmsx102.ccr.corp.intel.com \
--to=wenzhuo.lu@intel.com \
--cc=dev@dpdk.org \
--cc=lunyuanx.cui@intel.com \
--cc=stable@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).