From: Ferruh Yigit <ferruh.yigit@intel.com>
To: "Yang, Zhiyong" <zhiyong.yang@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: Thu, 23 Jul 2020 15:34:18 +0100 [thread overview]
Message-ID: <797d7f32-a6e9-e4ca-bad3-fe3693db9f29@intel.com> (raw)
In-Reply-To: <MN2PR11MB38727CF65215E5189DBB1A8794760@MN2PR11MB3872.namprd11.prod.outlook.com>
On 7/23/2020 10:23 AM, Yang, Zhiyong wrote:
>
> -----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>
>
> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> Acked-by: Zhiyong Yang <zhiyong.yang@intel.com>
>
Applied to dpdk-next-net/master, thanks.
Updated commit log as below:
doc: announce dpaa specific API parameter change
'port_id' storage size should be 'uint16_t', the API
'rte_pmd_dpaa_set_tx_loopback()' has it as 'uint8_t' but fixing it is an
ABI breakage, that is why planning the fix in v20.11 release where ABI
breakage is allowed.
prev parent reply other threads:[~2020-07-23 14:34 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
2020-07-23 14:34 ` Ferruh Yigit [this message]
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=797d7f32-a6e9-e4ca-bad3-fe3693db9f29@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=sachin.saxena@oss.nxp.com \
--cc=zhiyong.yang@intel.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).