From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, Ray Kinsella <mdr@ashroe.eu>,
Neil Horman <nhorman@tuxdriver.com>,
John McNamara <john.mcnamara@intel.com>,
"Marko Kovacevic" <marko.kovacevic@intel.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [dpdk-dev] [PATCH] doc: announce changes to eventdev public structures
Date: Sun, 2 Aug 2020 16:21:37 +0530 [thread overview]
Message-ID: <20200802105137.1666-1-pbhagavatula@marvell.com> (raw)
From: Pavan Nikhilesh <pbhagavatula@marvell.com>
Add 64 byte padding at the end of event device public structure to allow
future extensions.
Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
http://patches.dpdk.org/project/dpdk/list/?series=10728&state=*
doc/guides/rel_notes/deprecation.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index ea4cfa7a4..37c7c9029 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -151,3 +151,12 @@ Deprecation Notices
Python 2 support will be completely removed in 20.11.
In 20.08, explicit deprecation warnings will be displayed when running
scripts with Python 2.
+
+* eventdev: A 64 byte padding is added at the end of the following structures
+ in event device library to support future extensions:
+ ``rte_event_crypto_adapter_conf``, ``rte_event_eth_rx_adapter_conf``,
+ ``rte_event_eth_rx_adapter_queue_conf``, ``rte_event_eth_tx_adapter_conf``,
+ ``rte_event_timer_adapter_conf``, ``rte_event_timer_adapter_info``,
+ ``rte_event_dev_info``, ``rte_event_dev_config``, ``rte_event_queue_conf``,
+ ``rte_event_port_conf``, ``rte_event_timer_adapter``,
+ ``rte_event_timer_adapter_data``.
--
2.17.1
next reply other threads:[~2020-08-02 10:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 10:51 pbhagavatula [this message]
2020-08-03 6:14 ` Jerin Jacob
2020-08-03 7:29 ` [dpdk-dev] [PATCH v2] doc: add reserve fields " pbhagavatula
2020-08-04 10:41 ` Bruce Richardson
2020-08-04 11:37 ` Jerin Jacob
2020-08-04 14:24 ` Bruce Richardson
2020-08-04 16:03 ` Jerin Jacob
2020-08-04 16:24 ` Bruce Richardson
2020-08-04 17:18 ` Jerin Jacob
2020-08-05 9:18 ` Kinsella, Ray
2020-08-05 10:07 ` Bruce Richardson
2020-08-04 16:20 ` Stephen Hemminger
2020-08-05 8:46 ` Kinsella, Ray
2020-08-05 9:10 ` Jerin Jacob
2020-08-06 0:59 ` Stephen Hemminger
2020-08-06 16:57 ` 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=20200802105137.1666-1-pbhagavatula@marvell.com \
--to=pbhagavatula@marvell.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=john.mcnamara@intel.com \
--cc=marko.kovacevic@intel.com \
--cc=mdr@ashroe.eu \
--cc=nhorman@tuxdriver.com \
/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).