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 0/3] doc: fix some errors in hns3 guide
Date: Fri, 30 Jun 2023 15:37:34 +0800 [thread overview]
Message-ID: <20230630073737.20915-1-liudongdong3@huawei.com> (raw)
This patchset is to fix some errors in hns3 guide doc.
Dongdong Liu (3):
doc: fix invalid link in hns3 guide
doc: fix wrong syntax in hns3 guide
doc: fix wrong number of spaces in hns3 guide
doc/guides/nics/hns3.rst | 33 +++++++++++++++++++--------------
1 file changed, 19 insertions(+), 14 deletions(-)
--
2.22.0
next 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 Dongdong Liu [this message]
2023-06-30 7:37 ` [PATCH 1/3] doc: fix invalid link " Dongdong Liu
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-1-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).