From: Bruce Richardson <bruce.richardson@intel.com>
To: dev@dpdk.org
Cc: Bruce Richardson <bruce.richardson@intel.com>
Subject: [dpdk-dev] [PATCH 0/2] Deprecation notice updates
Date: Mon, 13 Jul 2020 13:31:03 +0100 [thread overview]
Message-ID: <20200713123105.513960-1-bruce.richardson@intel.com> (raw)
Put in deprecation notices in the 20.08 release for changes coming in 20.11.
Bruce Richardson (2):
doc: add deprecation notice for make build system removal
doc: add deprecation notice for change of rawdev APIs
doc/guides/rel_notes/deprecation.rst | 14 ++++++++++++++
1 file changed, 14 insertions(+)
--
2.25.1
next reply other threads:[~2020-07-13 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-13 12:31 Bruce Richardson [this message]
2020-07-13 12:31 ` [dpdk-dev] [PATCH 1/2] doc: add deprecation notice for make build system removal Bruce Richardson
2020-07-20 13:28 ` Ferruh Yigit
2020-07-20 13:38 ` Andrew Rybchenko
2020-07-20 16:51 ` Thomas Monjalon
2020-07-13 12:31 ` [dpdk-dev] [PATCH 2/2] doc: add deprecation notice for change of rawdev APIs Bruce Richardson
2020-07-13 12:48 ` Hemant Agrawal
2020-07-20 11:35 ` Ananyev, Konstantin
2020-07-23 1:55 ` Xu, Rosen
2020-07-23 7:38 ` Hemant Agrawal
2020-08-05 22:48 ` [dpdk-dev] [PATCH 0/2] Deprecation notice updates 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=20200713123105.513960-1-bruce.richardson@intel.com \
--to=bruce.richardson@intel.com \
--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;
as well as URLs for NNTP newsgroup(s).