DPDK patches and discussions
 help / color / mirror / Atom feed
From: John McNamara <john.mcnamara@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, John McNamara <john.mcnamara@intel.com>
Subject: [PATCH v1] doc: update release notes for 23.03
Date: Thu, 30 Mar 2023 17:09:05 +0100	[thread overview]
Message-ID: <20230330160905.18324-1-john.mcnamara@intel.com> (raw)

Fix grammar, spelling and formatting of DPDK 23.03 release notes.

Signed-off-by: John McNamara <john.mcnamara@intel.com>
---

* Minor fixes/changes only.


 doc/guides/rel_notes/release_23_03.rst | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/doc/guides/rel_notes/release_23_03.rst b/doc/guides/rel_notes/release_23_03.rst
index b93903447d..a31d34f5f5 100644
--- a/doc/guides/rel_notes/release_23_03.rst
+++ b/doc/guides/rel_notes/release_23_03.rst
@@ -71,7 +71,7 @@ New Features
 * **Added platform bus support.**
 
   A platform bus provides a way to use Linux platform devices which
-  are compatible with vfio-platform kernel driver.
+  are compatible with the do  vfio-platform kernel driver.
 
 * **Added ARM support for power monitor in the power management library.**
 
@@ -80,6 +80,9 @@ New Features
 
 * **Added Ethernet link speed for 400 Gb/s.**
 
+Added Ethernet link speed for 400 Gb/s since there are some devices already
+supporting that speed and it is well standardized in IEEE.
+
 * **Added support for mapping a queue with an aggregated port.**
 
   * Introduced new function ``rte_eth_dev_count_aggr_ports()``
@@ -88,6 +91,7 @@ New Features
     to map a Tx queue with an aggregated port of the DPDK port.
   * Added Rx affinity flow matching of an aggregated port.
 
+
 * **Added flow matching of IPv6 routing extension.**
 
   Added ``RTE_FLOW_ITEM_TYPE_IPV6_ROUTING_EXT``
@@ -113,7 +117,7 @@ New Features
 
 * **Added cross-port indirect action in asynchronous flow API.**
 
-  * Allowed to share indirect actions between ports by passing
+  * Enabled the ability to share indirect actions between ports by passing
     the flag ``RTE_FLOW_PORT_FLAG_SHARE_INDIRECT`` to ``rte_flow_configure()``.
   * Added ``host_port_id`` in ``rte_flow_port_attr`` structure
     to reference the port hosting the shared objects.
@@ -215,14 +219,14 @@ New Features
 
 * **Updated the eventdev reconfigure logic for service based adapters.**
 
-  * eventdev reconfig logic is enhanced to increment the
+  * The eventdev reconfigure logic was enhanced to increment the
     ``rte_event_dev_config::nb_single_link_event_port_queues`` parameter
     if event port config is of type ``RTE_EVENT_PORT_CFG_SINGLE_LINK``.
   * With this change, the application no longer needs to account for the
     ``rte_event_dev_config::nb_single_link_event_port_queues`` parameter
     required for eth_rx, eth_tx, crypto and timer eventdev adapters.
 
-* **Added pcap trace support in graph library.**
+* **Added PCAP trace support in graph library.**
 
   * Added support to capture packets at each graph node with packet metadata and
     node name.
@@ -263,8 +267,8 @@ API Changes
 
 * The telemetry command ``/eal/heap_info`` is fixed to print ``Heap_id``.
 
-* The experimental function ``rte_pcapng_copy`` was updated to support comment
-  section in enhanced packet block in the pcapng library.
+* The experimental function ``rte_pcapng_copy`` was updated to support a comment
+  section in enhanced packet block in the PcapNG library.
 
 * The experimental structures ``struct rte_graph_param``, ``struct rte_graph``
   and ``struct graph`` were updated to support pcap trace in the graph library.
-- 
2.31.1


             reply	other threads:[~2023-03-30 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 16:09 John McNamara [this message]
2023-03-30 19:19 ` Zhang, Fan
2023-03-31 12:52   ` Thomas Monjalon

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=20230330160905.18324-1-john.mcnamara@intel.com \
    --to=john.mcnamara@intel.com \
    --cc=dev@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).