From: Yong Wang <wang.yong19@zte.com.cn>
To: john.mcnamara@intel.com
Cc: dev@dpdk.org, Yong Wang <wang.yong19@zte.com.cn>
Subject: [dpdk-dev] [PATCH] doc: fix typo in release note
Date: Tue, 21 May 2019 04:46:49 -0400 [thread overview]
Message-ID: <1558428409-29815-1-git-send-email-wang.yong19@zte.com.cn> (raw)
The patch fixes some typoes in 19.02 release note.
Fixes: 6f04df497962 ("doc: add release notes for mlx5")
Fixes: bf9a90e2b562 ("doc: update release notes for 19.02")
Signed-off-by: Yong Wang <wang.yong19@zte.com.cn>
---
doc/guides/rel_notes/release_19_02.rst | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/doc/guides/rel_notes/release_19_02.rst b/doc/guides/rel_notes/release_19_02.rst
index b353620..0197f29 100644
--- a/doc/guides/rel_notes/release_19_02.rst
+++ b/doc/guides/rel_notes/release_19_02.rst
@@ -103,8 +103,8 @@ New Features
* Fixed ``imissed`` counter to be reported through ``rte_eth_stats`` instead
of ``rte_eth_xstats``.
* Added packet header modification through Direct Verbs flow driver.
- * Added ConnectX-6 PCI device ID to be proved by ``mlx5`` driver.
- * Added flow counter support to Direct Verbs flow driver though DevX.
+ * Added ConnectX-6 PCI device ID to be probed by ``mlx5`` driver.
+ * Added flow counter support to Direct Verbs flow driver through DevX.
* Renamed build options for the glue layer to
``CONFIG_RTE_IBVERBS_LINK_DLOPEN`` for make and ``ibverbs_link`` for meson.
* Added static linkage of ``mlx`` dependency.
@@ -135,7 +135,7 @@ New Features
This SW-assisted VDPA live migration facility helps VDPA devices without
logging capability to perform live migration, a mediated SW relay can help
- devices to track dirty pages caused by DMA. the IFC driver has enabled this
+ devices to track dirty pages caused by DMA. The IFC driver has enabled this
SW-assisted live migration mode.
* **Added security checks to the cryptodev symmetric session operations.**
@@ -215,7 +215,7 @@ API Changes
by the existing ``rte_bsf32`` function.
* eal: Segment fd API on Linux now sets error code to ``ENOTSUP`` in more cases
- where segment the fd API is not expected to be supported:
+ where the segment fd API is not expected to be supported:
- On attempt to get a segment fd for an externally allocated memory segment
- In cases where memfd support would have been required to provide segment
--
1.8.3.1
next reply other threads:[~2019-05-21 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 8:46 Yong Wang [this message]
2019-05-21 14:33 ` Ferruh Yigit
2019-05-21 16:30 ` Kevin Traynor
2019-07-30 11:24 ` Mcnamara, John
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=1558428409-29815-1-git-send-email-wang.yong19@zte.com.cn \
--to=wang.yong19@zte.com.cn \
--cc=dev@dpdk.org \
--cc=john.mcnamara@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).