From: David Marchand <david.marchand@redhat.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, bluca@debian.org,
bruce.richardson@intel.com, mb@smartsharesystems.com
Subject: [PATCH] doc: announce change for building deprecated libraries
Date: Wed, 28 Jun 2023 15:43:15 +0200 [thread overview]
Message-ID: <20230628134315.551591-1-david.marchand@redhat.com> (raw)
As part of a larger work on selecting parts of DPDK of interests for
users, enabling deprecated libraries won't be done via the disable_libs
build option anymore.
An example of the new build option can be found at:
https://patchwork.dpdk.org/project/dpdk/patch/20230628132004.340074-2-david.marchand@redhat.com/
Signed-off-by: David Marchand <david.marchand@redhat.com>
---
doc/guides/rel_notes/deprecation.rst | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 8e1cdd677a..f148d7c80a 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -11,6 +11,10 @@ here.
Deprecation Notices
-------------------
+* build: Enabling deprecated libraries (``flow_classify``, ``kni``) won't be
+ possible anymore through the use of the ``disable_libs`` build option. A
+ new build option for deprecated libraries will be introduced instead.
+
* kvargs: The function ``rte_kvargs_process`` will get a new parameter
for returning key match count. It will ease handling of no-match case.
--
2.40.1
next reply other threads:[~2023-06-28 13:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 13:43 David Marchand [this message]
2023-06-28 14:56 ` Morten Brørup
2023-07-17 13:24 ` Bruce Richardson
2023-07-28 9:59 ` 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=20230628134315.551591-1-david.marchand@redhat.com \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=mb@smartsharesystems.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).