From: Timothy McDaniel <timothy.mcdaniel@intel.com>
Cc: dev@dpdk.org, erik.g.carrillo@intel.com,
harry.van.haaren@intel.com, jerinj@marvell.com,
thomas@monjalon.net
Subject: [dpdk-dev] [PATCH 4/4] doc: update 21.05 release notes to announce removal of DLB V1
Date: Mon, 1 Mar 2021 11:00:59 -0600 [thread overview]
Message-ID: <1614618060-12773-5-git-send-email-timothy.mcdaniel@intel.com> (raw)
In-Reply-To: <1614618060-12773-1-git-send-email-timothy.mcdaniel@intel.com>
Support for DLB v1 is being removed from dpdk in 21.05.
Signed-off-by: Timothy McDaniel <timothy.mcdaniel@intel.com>
---
doc/guides/rel_notes/release_21_05.rst | 2 ++
1 file changed, 2 insertions(+)
diff --git a/doc/guides/rel_notes/release_21_05.rst b/doc/guides/rel_notes/release_21_05.rst
index 5aa9ed7db..a941d89ef 100644
--- a/doc/guides/rel_notes/release_21_05.rst
+++ b/doc/guides/rel_notes/release_21_05.rst
@@ -68,6 +68,8 @@ Removed Items
Also, make sure to start the actual text at the margin.
=======================================================
+* Removed support for DLB V1 hardware. This is not a broad market device,
+ and existing customers already obtain the source code directly from Intel.
API Changes
-----------
--
2.23.0
next prev parent reply other threads:[~2021-03-01 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-01 17:00 [dpdk-dev] [PATCH 0/4] Remove Support For " Timothy McDaniel
2021-03-01 17:00 ` [dpdk-dev] [PATCH 1/4] event/dlb: remove DLB V1 from build Timothy McDaniel
2021-03-01 17:00 ` [dpdk-dev] [PATCH 2/4] event/dlb: remove DLB V1 documentation Timothy McDaniel
2021-03-01 17:00 ` [dpdk-dev] [PATCH 3/4] event/dlb: remove DLB V1 source code Timothy McDaniel
2021-03-01 17:00 ` Timothy McDaniel [this message]
2021-03-07 15:34 ` [dpdk-dev] [PATCH 0/4] Remove Support For DLB V1 Jerin Jacob
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=1614618060-12773-5-git-send-email-timothy.mcdaniel@intel.com \
--to=timothy.mcdaniel@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=harry.van.haaren@intel.com \
--cc=jerinj@marvell.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 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).