From: "Kovacevic, Marko" <marko.kovacevic@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>,
"Xing, Beilei" <beilei.xing@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
"Zhang, Qi Z" <qi.z.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"Zhang, Helin" <helin.zhang@intel.com>,
"Wu, Jingjing" <jingjing.wu@intel.com>
Subject: Re: [dpdk-dev] [PATCH V3] doc: add known PHY link up issue for i40e
Date: Fri, 16 Nov 2018 09:41:11 +0000 [thread overview]
Message-ID: <6DC05C7C5F25994B81B3F2F214251F6602050C8E@IRSMSX104.ger.corp.intel.com> (raw)
In-Reply-To: <1542335898-148573-1-git-send-email-jia.guo@intel.com>
One very small spelling fix
> +PHY link up fails when rebinding i40e NICs to kernel driver
> +-----------------------------------------------------------
> +
> +**Description**:
> + Some kernel drivers are not able to handle the link status correctly
> + after DPDK application sets the PHY to link down.
> +
> +**Implication**:
> + The link status can't be set to "up" after the NIC is rebound to the
> + kernel driver. Before a DPDK application quits it will invokes the
Invokes/ invoke
Everything else looks fine to me.
You can add my ack in the next quick fix.
Acked-by: Marko Kovacevic <marko.kovacevic@intel.com>
next prev parent reply other threads:[~2018-11-16 9:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 11:08 [dpdk-dev] [PATCH] " Jeff Guo
2018-10-19 18:05 ` Zhang, Qi Z
2018-11-08 7:05 ` Guo, Jia
2018-11-08 7:17 ` [dpdk-dev] [PATCH V2] " Jeff Guo
2018-11-08 17:48 ` Zhang, Qi Z
2018-11-09 2:21 ` Jeff Guo
2018-11-09 16:31 ` Zhang, Qi Z
2018-11-16 2:38 ` [dpdk-dev] [PATCH V3] " Jeff Guo
2018-11-16 9:41 ` Kovacevic, Marko [this message]
2018-11-16 19:32 ` Zhang, Qi Z
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=6DC05C7C5F25994B81B3F2F214251F6602050C8E@IRSMSX104.ger.corp.intel.com \
--to=marko.kovacevic@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@intel.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).