From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v3 2/4] mbuf: make rte_mbuf_dynfield API's stable
Date: Wed, 1 Sep 2021 09:43:00 +0300 [thread overview]
Message-ID: <cf99f034-0d36-a817-2a8c-448e12e53d6d@oktetlabs.ru> (raw)
In-Reply-To: <20210831193507.43426-3-stephen@networkplumber.org>
On 8/31/21 10:35 PM, Stephen Hemminger wrote:
> These functions to register dynamic fields were added in 20.11
> and should be promoted to stable.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
Acked-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
next prev parent reply other threads:[~2021-09-01 6:43 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-25 15:52 [dpdk-dev] [PATCH 0/2] mbuf: unmark experimental API's Stephen Hemminger
2021-08-25 15:52 ` [dpdk-dev] [PATCH 1/2] mbuf: take experimental of mbuf copy and bulk free Stephen Hemminger
2021-08-25 15:52 ` [dpdk-dev] [PATCH 2/2] mbuf: remove experimental from dynamic field support Stephen Hemminger
2021-08-25 22:09 ` [dpdk-dev] [PATCH v2 0/3] mbuf: experimental tag changes Stephen Hemminger
2021-08-25 22:09 ` [dpdk-dev] [PATCH v2 1/3] mbuf: take experimental of mbuf copy and bulk free Stephen Hemminger
2021-08-25 22:09 ` [dpdk-dev] [PATCH v2 2/3] mbuf: remove experimental from dynamic field support Stephen Hemminger
2021-08-25 22:09 ` [dpdk-dev] [PATCH v2 3/3] mbuf: mark function rte_mbuf_tx_offload with __rte_expermental Stephen Hemminger
2021-08-31 19:35 ` [dpdk-dev] [PATCH v3 0/4] mbuf: promote experimental API's to stable Stephen Hemminger
2021-08-31 19:35 ` [dpdk-dev] [PATCH v3 1/4] mbuf: make rte_pktmbuf_free_bulk and rte_pktmbuf_copy stable API's Stephen Hemminger
2021-09-01 6:42 ` Andrew Rybchenko
2021-09-16 11:55 ` Olivier Matz
2021-08-31 19:35 ` [dpdk-dev] [PATCH v3 2/4] mbuf: make rte_mbuf_dynfield API's stable Stephen Hemminger
2021-09-01 6:43 ` Andrew Rybchenko [this message]
2021-09-16 11:56 ` Olivier Matz
2021-08-31 19:35 ` [dpdk-dev] [PATCH v3 3/4] mbuf: make rte_mbuf_tx_offload as stable Stephen Hemminger
2021-09-01 6:45 ` Andrew Rybchenko
2021-09-01 17:14 ` Stephen Hemminger
2021-09-16 12:14 ` Olivier Matz
2021-10-02 9:34 ` David Marchand
2021-08-31 19:35 ` [dpdk-dev] [PATCH v3 4/4] mbuf: make rte_mbuf_check part of stable API Stephen Hemminger
2021-09-01 6:46 ` Andrew Rybchenko
2021-09-01 6:49 ` Andrew Rybchenko
2021-09-16 12:35 ` Olivier Matz
2021-10-04 19:32 ` [dpdk-dev] [PATCH v4 0/5] mbuf: promote experimental API's to stable Stephen Hemminger
2021-10-04 19:32 ` [dpdk-dev] [PATCH v4 1/5] mbuf: make rte_pktmbuf_free_bulk and rte_pktmbuf_copy stable API's Stephen Hemminger
2021-10-04 19:32 ` [dpdk-dev] [PATCH v4 2/5] mbuf: make rte_mbuf_dynfield API's stable Stephen Hemminger
2021-10-04 19:33 ` [dpdk-dev] [PATCH v4 3/5] mbuf: make rte_mbuf_check part of stable API Stephen Hemminger
2021-10-04 19:33 ` [dpdk-dev] [PATCH v4 4/5] mbuf: make rte_mbuf_tx_offload as stable Stephen Hemminger
2021-10-05 7:27 ` Olivier Matz
2021-10-05 8:17 ` Ananyev, Konstantin
2021-10-04 19:33 ` [dpdk-dev] [PATCH v4 5/5] mbuf: mark rte_mbuf_to_priv " Stephen Hemminger
2021-10-05 7:31 ` Olivier Matz
2021-10-05 8:20 ` [dpdk-dev] [PATCH v4 0/5] mbuf: promote experimental API's to stable David Marchand
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=cf99f034-0d36-a817-2a8c-448e12e53d6d@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
/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).