From: Dongdong Liu <liudongdong3@huawei.com>
To: <dev@dpdk.org>, <ferruh.yigit@amd.com>, <thomas@monjalon.net>,
<andrew.rybchenko@oktetlabs.ru>
Cc: <stable@dpdk.org>
Subject: [PATCH 1/3] doc: fix invalid link in hns3 guide
Date: Fri, 30 Jun 2023 15:37:35 +0800 [thread overview]
Message-ID: <20230630073737.20915-2-liudongdong3@huawei.com> (raw)
In-Reply-To: <20230630073737.20915-1-liudongdong3@huawei.com>
The LSC support of Vf driver depends on a patch link in kernel pf driver.
But current the link is invalid, so fixes it.
Add a blank line after the link.
Fixes: 80006b598730 ("doc: add link status event requirements in hns3 guide")
Cc: stable@dpdk.org
Signed-off-by: Dongdong Liu <liudongdong3@huawei.com>
---
doc/guides/nics/hns3.rst | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/doc/guides/nics/hns3.rst b/doc/guides/nics/hns3.rst
index 45f9a99a89..a6f3a5eb9e 100644
--- a/doc/guides/nics/hns3.rst
+++ b/doc/guides/nics/hns3.rst
@@ -54,7 +54,8 @@ 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>`_.
+`<https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=18b6e31f8bf4ac7af7b057228f38a5a530378e4e>`_.
+
Note: The patch has been uploaded to 5.13 of the Linux kernel mainline.
--
2.22.0
next prev parent reply other threads:[~2023-06-30 7:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 7:37 [PATCH 0/3] doc: fix some errors " Dongdong Liu
2023-06-30 7:37 ` Dongdong Liu [this message]
2023-06-30 7:37 ` [PATCH 2/3] doc: fix wrong syntax " Dongdong Liu
2023-06-30 7:37 ` [PATCH 3/3] doc: fix wrong number of spaces " Dongdong Liu
2023-06-30 9:42 ` [PATCH 0/3] doc: fix some errors " 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=20230630073737.20915-2-liudongdong3@huawei.com \
--to=liudongdong3@huawei.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=stable@dpdk.org \
--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 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).