From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
"Sachin Saxena (OSS)" <sachin.saxena@oss.nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/dpaa: announce extended definition of port_id in API 'rte_pmd_dpaa_set_tx_loopback'
Date: Tue, 14 Jul 2020 11:57:45 +0000 [thread overview]
Message-ID: <DB7PR04MB44595245BDF39E350D45B29E89610@DB7PR04MB4459.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <649640a1-3b9f-8af5-2b67-7be7db543bc2@intel.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
-----Original Message-----
From: dev <dev-bounces@dpdk.org> On Behalf Of Ferruh Yigit
Sent: Tuesday, July 14, 2020 5:07 PM
To: Sachin Saxena (OSS) <sachin.saxena@oss.nxp.com>; dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/dpaa: announce extended definition of port_id in API 'rte_pmd_dpaa_set_tx_loopback'
On 7/14/2020 12:32 PM, Sachin Saxena (OSS) wrote:
> 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.
>
Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
next prev parent reply other threads:[~2020-07-14 11:57 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 [this message]
2020-07-23 9:23 ` Yang, Zhiyong
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=DB7PR04MB44595245BDF39E350D45B29E89610@DB7PR04MB4459.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.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).