From: "Yang, Zhiyong" <zhiyong.yang@intel.com>
To: "Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Yigit, Ferruh" <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/dpaa: announce extended definition of port_id in API 'rte_pmd_dpaa_set_tx_loopback'
Date: Thu, 23 Jul 2020 09:23:10 +0000 [thread overview]
Message-ID: <MN2PR11MB38727CF65215E5189DBB1A8794760@MN2PR11MB3872.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20200714113242.20306-1-sachin.saxena@oss.nxp.com>
Acked-by: Zhiyong Yang <zhiyong.yang@intel.com>
-----Original Message-----
From: dev <dev-bounces@dpdk.org> On Behalf Of Sachin Saxena (OSS)
Sent: Tuesday, July 14, 2020 7:33 PM
To: dev@dpdk.org; Yigit, Ferruh <ferruh.yigit@intel.com>
Subject: [dpdk-dev] [PATCH] net/dpaa: announce extended definition of port_id in API 'rte_pmd_dpaa_set_tx_loopback'
From: Sachin Saxena <sachin.saxena@oss.nxp.com>
Signed-off-by: Sachin Saxena <sachin.saxena@oss.nxp.com>
---
doc/guides/rel_notes/deprecation.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index a58a17946..a0715e587 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -142,3 +142,6 @@ 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.
+
+* pmd_dpaa: The API ``rte_pmd_dpaa_set_tx_loopback`` will have extended ``port_id``
+ definition from uint8_t to uint16_t.
--
2.24.1
next prev parent reply other threads:[~2020-07-23 9:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-14 11:32 Sachin Saxena (OSS)
2020-07-14 11:36 ` Ferruh Yigit
2020-07-14 11:57 ` Hemant Agrawal
2020-07-23 9:23 ` Yang, Zhiyong [this message]
2020-07-23 14:34 ` Ferruh Yigit
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=MN2PR11MB38727CF65215E5189DBB1A8794760@MN2PR11MB3872.namprd11.prod.outlook.com \
--to=zhiyong.yang@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=sachin.saxena@oss.nxp.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).