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>,
	John McNamara <john.mcnamara@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>
Subject: [dpdk-dev] [PATCH] doc: clarify PMD order in release notes
Date: Fri,  9 Apr 2021 16:21:45 +0100	[thread overview]
Message-ID: <20210409152145.2550755-1-ferruh.yigit@intel.com> (raw)

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>
---
Cc: Thomas Monjalon <thomas@monjalon.net>
---
 doc/guides/rel_notes/release_21_05.rst | 1 +
 1 file changed, 1 insertion(+)

diff --git a/doc/guides/rel_notes/release_21_05.rst b/doc/guides/rel_notes/release_21_05.rst
index e739153b509f..20cca03cbb9d 100644
--- a/doc/guides/rel_notes/release_21_05.rst
+++ b/doc/guides/rel_notes/release_21_05.rst
@@ -45,6 +45,7 @@ New Features
      * Core libs (EAL, mempool, ring, mbuf, buses)
      * Device abstraction libs and PMDs
        - ethdev (lib, PMDs)
+         * PMDs are ordered alphabetically on vendor name
        - cryptodev (lib, PMDs)
        - eventdev (lib, PMDs)
        - etc
-- 
2.30.2


             reply	other threads:[~2021-04-09 15:21 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-09 15:21 Ferruh Yigit [this message]
2021-04-09 15:34 ` [dpdk-dev] [PATCH] doc: clarify PMD order in release notes Thomas Monjalon
2021-05-12 16:04 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2021-05-19 20:42   ` 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=20210409152145.2550755-1-ferruh.yigit@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.mcnamara@intel.com \
    --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.