DPDK-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, Bruce Richardson <bruce.richardson@intel.com>
Subject: [PATCH 5/6] doc/rel_notes: fix style of API changes section
Date: Tue, 21 Jul 2026 16:13:24 +0100	[thread overview]
Message-ID: <20260721151325.2698283-6-bruce.richardson@intel.com> (raw)
In-Reply-To: <20260721151325.2698283-1-bruce.richardson@intel.com>

The format of the API section as documented does not have headings in
bold. This simpler format is also what is used for the 25.11 and
previous release notes. Update text for 26.07 to match the documented
and previously used style.

Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
---
 doc/guides/rel_notes/release_26_07.rst | 15 +++++----------
 1 file changed, 5 insertions(+), 10 deletions(-)

diff --git a/doc/guides/rel_notes/release_26_07.rst b/doc/guides/rel_notes/release_26_07.rst
index b3c23b73a1..fca135569f 100644
--- a/doc/guides/rel_notes/release_26_07.rst
+++ b/doc/guides/rel_notes/release_26_07.rst
@@ -317,13 +317,9 @@ API Changes
    Also, make sure to start the actual text at the margin.
    =======================================================
 
-* **eal: promoted timing-safe memory comparison from experimental to stable.**
+* eal: Promoted ``rte_memeq_timingsafe()`` from experimental to stable.
 
-  The inline function ``rte_memeq_timingsafe()`` is no longer marked experimental.
-
-* **ethdev: promoted flow metadata API from experimental to stable.**
-
-  The following ethdev symbols are no longer marked experimental:
+* ethdev: Promoted the following flow metadata symbols from experimental to stable:
 
   - ``rte_flow_dynf_metadata_register``
   - ``rte_flow_dynf_metadata_offs``
@@ -332,16 +328,15 @@ API Changes
   - ``rte_flow_dynf_metadata_get``
   - ``rte_flow_dynf_metadata_set``
 
-* **mlx5: promoted driver event and steering management APIs from experimental to stable.**
-
-  The following mlx5 functions are no longer marked experimental:
+* mlx5: Promoted the following driver event and steering management functions
+  from experimental to stable:
 
   - ``rte_pmd_mlx5_driver_event_cb_register``
   - ``rte_pmd_mlx5_driver_event_cb_unregister``
   - ``rte_pmd_mlx5_enable_steering``
   - ``rte_pmd_mlx5_disable_steering``
 
-* **ip_frag: changed handling of malformed fragments.**
+* ip_frag: Changed handling of malformed fragments.
 
   - Duplicate fragments are tolerated instead of failing reassembly.
   - Overlapping fragments are rejected on arrival rather than during reassembly.
-- 
2.53.0


  parent reply	other threads:[~2026-07-21 15:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21 15:13 [PATCH 0/6] doc/rel_notes: updates to 26.07 doc Bruce Richardson
2026-07-21 15:13 ` [PATCH 1/6] doc/rel_notes: remove bullets for single items Bruce Richardson
2026-07-21 15:13 ` [PATCH 2/6] doc/rel_notes: move mempool change to first item Bruce Richardson
2026-07-21 15:13 ` [PATCH 3/6] doc/rel_notes: keep library updates together Bruce Richardson
2026-07-21 19:37   ` Thomas Monjalon
2026-07-22  7:59     ` Bruce Richardson
2026-07-21 15:13 ` [PATCH 4/6] doc/rel_notes: fix driver ordering Bruce Richardson
2026-07-21 15:13 ` Bruce Richardson [this message]
2026-07-21 15:13 ` [PATCH 6/6] doc/rel_notes: minor style fixes Bruce Richardson
2026-07-21 17:24 ` [PATCH 0/6] doc/rel_notes: updates to 26.07 doc Morten Brørup

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=20260721151325.2698283-6-bruce.richardson@intel.com \
    --to=bruce.richardson@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