All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: dev@dpdk.org
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH v2] doc: clarify PMD order in release notes
Date: Wed, 12 May 2021 17:04:43 +0100	[thread overview]
Message-ID: <20210512160443.1155817-1-ferruh.yigit@intel.com> (raw)
In-Reply-To: <20210409152145.2550755-1-ferruh.yigit@intel.com>

PMD updates are expected in alphabetical order based on their vendor
name. Clarify this expectation in the section comment.

Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
---
v2:
* Do not restrict clarification for ethdev
---
 doc/guides/rel_notes/release_21_05.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/guides/rel_notes/release_21_05.rst b/doc/guides/rel_notes/release_21_05.rst
index b144ae9e9dbc..b56d66d2a245 100644
--- a/doc/guides/rel_notes/release_21_05.rst
+++ b/doc/guides/rel_notes/release_21_05.rst
@@ -43,7 +43,7 @@ New Features
 
      Suggested order in release notes items:
      * Core libs (EAL, mempool, ring, mbuf, buses)
-     * Device abstraction libs and PMDs
+     * Device abstraction libs and PMDs (PMDs ordered alphabetically by vendor name)
        - ethdev (lib, PMDs)
        - cryptodev (lib, PMDs)
        - eventdev (lib, PMDs)
-- 
2.31.1


  parent reply	other threads:[~2021-05-12 16:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 15:21 [dpdk-dev] [PATCH] doc: clarify PMD order in release notes Ferruh Yigit
2021-04-09 15:34 ` Thomas Monjalon
2021-05-12 16:04 ` Ferruh Yigit [this message]
2021-05-19 20:42   ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2021-05-19 23:06     ` Ferruh Yigit
2021-05-20  7:34       ` 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=20210512160443.1155817-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.