DPDK patches and discussions
 help / color / mirror / Atom feed
From: yaochuhong <ych@panath.cn>
To: shijith.thotton@cavium.com
Cc: dev@dpdk.org, yaochuhong <ych@panath.cn>
Subject: [dpdk-dev] [PATCH 2/3] fix Coding Style
Date: Mon, 21 May 2018 09:20:54 +0800	[thread overview]
Message-ID: <1526865655-59863-2-git-send-email-ych@panath.cn> (raw)
In-Reply-To: <1526865655-59863-1-git-send-email-ych@panath.cn>

---
 drivers/net/liquidio/lio_ethdev.c | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)
 mode change 100755 => 100644 drivers/net/liquidio/lio_ethdev.c

diff --git a/drivers/net/liquidio/lio_ethdev.c b/drivers/net/liquidio/lio_ethdev.c
old mode 100755
new mode 100644
index bd47911..0a6eb55
--- a/drivers/net/liquidio/lio_ethdev.c
+++ b/drivers/net/liquidio/lio_ethdev.c
@@ -1405,10 +1405,7 @@ struct rte_lio_xstats_name_off {
 	/* Configure RSS if device configured with multiple RX queues. */
 	lio_dev_mq_rx_configure(eth_dev);
 
-    /* Before update the link info, set link_status64 to 0,
-     * Otherwise, when eth_dev->data->mtu != mtu, the link state information cannot be obtained, 
-     * and lio_dev->intf_open will be set to 0.
-     */
+	/* Before update the link info, must set link_status64 to 0. */
     lio_dev->linfo.link.link_status64 = 0;
     
 	/* start polling for lsc */
-- 
1.8.3.1

  reply	other threads:[~2018-05-21  1:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21  1:20 [dpdk-dev] [PATCH 1/3] net liquidio fix Unable to update lio_dev->linfo.link var yaochuhong
2018-05-21  1:20 ` yaochuhong [this message]
2018-05-21  1:20 ` [dpdk-dev] [PATCH 3/3] add signoff yaochuhong
2018-05-21 10:07   ` Ferruh Yigit
2018-05-21 10:11     ` Yao chuhong
2018-05-21  6:55 ` [dpdk-dev] [PATCH 1/3] net liquidio fix Unable to update lio_dev->linfo.link var Stephen Hemminger

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=1526865655-59863-2-git-send-email-ych@panath.cn \
    --to=ych@panath.cn \
    --cc=dev@dpdk.org \
    --cc=shijith.thotton@cavium.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).