From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: ferruh.yigit@intel.com, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH v2] doc: add link status event pre-conditions
Date: Fri, 2 Jul 2021 11:55:03 +0300 [thread overview]
Message-ID: <bbd2eb72-6cfa-4f6b-035a-e2fb00a87f37@oktetlabs.ru> (raw)
In-Reply-To: <1625018183-58204-1-git-send-email-humin29@huawei.com>
On 6/30/21 4:56 AM, Min Hu (Connor) wrote:
> From: Chengwen Feng <fengchengwen@huawei.com>
>
> This patch adds link status event pre-conditions.
>
> Signed-off-by: Chengwen Feng <fengchengwen@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
> ---
> v2:
> * not modified, only waiting for 5.13 kernel released.
> ---
> doc/guides/nics/hns3.rst | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst
> index cf72810..c5c55d3 100644
> --- a/doc/guides/nics/hns3.rst
> +++ b/doc/guides/nics/hns3.rst
> @@ -115,6 +115,16 @@ Runtime Config Options
> For example::
> -a 0000:7d:00.0,dev_caps_mask=0xF
>
> +Link status event Pre-conditions
> +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> +
> +Firmware 1.8.0.0 and later versions support reporting link changes to the PF.
> +Therefore, to use the LSC for the PF driver, ensure that the firmware version
> +also supports reporting link changes.
> +If the VF driver needs to support LSC, special patch must be added:
> +`<https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/net/ethernet/hisilicon/hns3?h=next-20210428&id=18b6e31f8bf4ac7af7b057228f38a5a530378e4e>`_.
> +Note: The patch has been uploaded to 5.13 of the Linux kernel mainline.
> +
> Driver compilation and testing
> ------------------------------
>
>
I've added extra empty lines before new section and changed
prefix to net/hns3 since doc sounds very misleading for me
here.
net/hns3: add link status event pre-conditions
Add link status event pre-conditions in the driver documentation.
Applied, thanks.
@Thomas I'm not 100% sure about such links in the
documentation. Please, double-check.
next prev parent reply other threads:[~2021-07-02 8:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-07 9:08 [dpdk-dev] [PATCH 0/6] bugfix for hns3 PMD Min Hu (Connor)
2021-05-07 9:08 ` [dpdk-dev] [PATCH 1/6] net/hns3: return code when PCI config space write fail Min Hu (Connor)
2021-05-07 9:08 ` [dpdk-dev] [PATCH 2/6] net/hns3: fix logging info when clear all FDIR rules Min Hu (Connor)
2021-05-07 9:08 ` [dpdk-dev] [PATCH 3/6] net/hns3: clear hash map " Min Hu (Connor)
2021-05-07 9:08 ` [dpdk-dev] [PATCH 4/6] net/hns3: fix VF setting alive order problem Min Hu (Connor)
2021-05-07 9:08 ` [dpdk-dev] [PATCH 5/6] net/hns3: fix out param not set when query FDIR counter Min Hu (Connor)
2021-05-07 9:08 ` [dpdk-dev] [PATCH 6/6] doc: add link status event pre-conditions Min Hu (Connor)
2021-05-11 16:14 ` Ferruh Yigit
2021-05-12 1:05 ` Min Hu (Connor)
2021-06-30 2:00 ` Min Hu (Connor)
2021-06-30 1:56 ` [dpdk-dev] [PATCH v2] " Min Hu (Connor)
2021-07-02 8:55 ` Andrew Rybchenko [this message]
2021-07-02 12:35 ` Thomas Monjalon
2021-07-02 12:58 ` Andrew Rybchenko
2021-07-04 19:42 ` Thomas Monjalon
2021-05-11 16:30 ` [dpdk-dev] [PATCH 0/6] bugfix for hns3 PMD Ferruh Yigit
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=bbd2eb72-6cfa-4f6b-035a-e2fb00a87f37@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.