public inbox for dev@dpdk.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Stephen Hemminger <stephen@networkplumber.org>
Subject: [PATCH v2 7/8] doc: correct alphabetical ordering in ethdev toctree
Date: Wed, 28 Jan 2026 11:46:06 -0800	[thread overview]
Message-ID: <20260128194722.480862-8-stephen@networkplumber.org> (raw)
In-Reply-To: <20260128194722.480862-1-stephen@networkplumber.org>

The toctree entries should be alphabetically ordered for consistency
with DPDK documentation guidelines. Move "flow_offload" before
"qos_framework" and "switch_representation" to maintain alphabetical
order.

Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
---
 doc/guides/prog_guide/ethdev/index.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/guides/prog_guide/ethdev/index.rst b/doc/guides/prog_guide/ethdev/index.rst
index 392ced0a2e..82a749e2b3 100644
--- a/doc/guides/prog_guide/ethdev/index.rst
+++ b/doc/guides/prog_guide/ethdev/index.rst
@@ -8,8 +8,8 @@ Ethernet Device Library
     :maxdepth: 1
 
     ethdev
-    switch_representation
     flow_offload
-    traffic_metering_and_policing
-    traffic_management
     qos_framework
+    switch_representation
+    traffic_management
+    traffic_metering_and_policing
-- 
2.51.0


  parent reply	other threads:[~2026-01-28 19:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-16 21:29 [PATCH 0/5] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-16 21:29 ` [PATCH 1/5] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 2/5] doc: correct grammar in rte_flow guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 3/5] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 4/5] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-16 21:29 ` [PATCH 5/5] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:45 ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 1/8] doc: correct grammar and punctuation errors in ethdev guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 2/8] doc: correct grammar in flow guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 3/8] doc: correct grammar in QoS framework guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 4/8] doc: correct typos in switch representation guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 5/8] doc: correct typos in traffic management guide Stephen Hemminger
2026-01-28 19:46   ` [PATCH v2 6/8] doc: correct grammar and improve clarity in ethdev guide Stephen Hemminger
2026-03-25 11:41     ` Thomas Monjalon
2026-01-28 19:46   ` Stephen Hemminger [this message]
2026-03-25 11:45     ` [PATCH v2 7/8] doc: correct alphabetical ordering in ethdev toctree Thomas Monjalon
2026-01-28 19:46   ` [PATCH v2 8/8] doc: correct grammar and improve clarity in MTR guide Stephen Hemminger
2026-02-05 21:29   ` [PATCH v2 0/8] doc: ethdev documentation grammar and typo corrections Stephen Hemminger

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=20260128194722.480862-8-stephen@networkplumber.org \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    /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