From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Haiyue Wang <haiyue.wang@intel.com>, <dev@dpdk.org>
Cc: Ray Kinsella <mdr@ashroe.eu>, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v2] ethdev: promote burst mode API to stable
Date: Wed, 15 Sep 2021 09:46:43 +0100 [thread overview]
Message-ID: <5b30c936-60e7-350d-77a2-b362fd1e0b03@intel.com> (raw)
In-Reply-To: <67e74f56-f976-1228-30cf-86b64c507cff@oktetlabs.ru>
On 9/6/2021 7:36 AM, Andrew Rybchenko wrote:
> On 9/6/21 8:56 AM, Haiyue Wang wrote:
>> The DPDK Symbol Bot reports:
>> Please note the symbols listed below have expired. In line with the
>> DPDK ABI policy, they should be scheduled for removal, in the next
>> DPDK release.
>>
>> Symbol
>> rte_eth_rx_burst_mode_get
>> rte_eth_tx_burst_mode_get
>>
>> Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
>> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com>
>> Acked-by: Ray Kinsella <mdr@ashroe.eu>
>
> Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2021-09-15 8:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 5:07 [dpdk-dev] [PATCH v1 0/3] Promote some " Haiyue Wang
2021-09-01 5:07 ` [dpdk-dev] [PATCH v1 1/3] net/ixgbe: promote " Haiyue Wang
2021-09-01 9:02 ` Ferruh Yigit
2021-09-01 11:13 ` Wang, Haiyue
2021-09-01 13:55 ` Kinsella, Ray
2021-09-01 5:07 ` [dpdk-dev] [PATCH v1 2/3] net/ice: " Haiyue Wang
2021-09-01 5:07 ` [dpdk-dev] [PATCH v1 3/3] ethdev: promote burst mode " Haiyue Wang
2021-09-01 9:07 ` Ferruh Yigit
2021-09-01 13:49 ` Kinsella, Ray
2021-09-06 5:56 ` [dpdk-dev] [PATCH v2] " Haiyue Wang
2021-09-06 6:36 ` Andrew Rybchenko
2021-09-15 8:46 ` 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=5b30c936-60e7-350d-77a2-b362fd1e0b03@intel.com \
--to=ferruh.yigit@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=haiyue.wang@intel.com \
--cc=mdr@ashroe.eu \
--cc=thomas@monjalon.net \
/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).