DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kinsella, Ray" <mdr@ashroe.eu>
To: Anatoly Burakov <anatoly.burakov@intel.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v1 3/7] eal: promote malloc API's to stable
Date: Fri, 10 Sep 2021 16:53:42 +0100	[thread overview]
Message-ID: <30ebe2a8-f555-6ecc-6853-968fcac1c843@ashroe.eu> (raw)
In-Reply-To: <ec3f9b7e899f1c4efe2d5ba75028efeabdc83b06.1631277001.git.anatoly.burakov@intel.com>



On 10/09/2021 13:30, Anatoly Burakov wrote:
> As per ABI policy, move the formerly experimental API's to the stable
> section.
> 
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
> ---
>  lib/eal/include/rte_malloc.h | 10 ----------
>  lib/eal/version.map          | 20 ++++++++++----------
>  2 files changed, 10 insertions(+), 20 deletions(-)
> 
Acked-by: Ray Kinsella <mdr@ashroe.eu>

  reply	other threads:[~2021-09-10 15:53 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-10 12:30 [dpdk-dev] [PATCH v1 1/7] eal: promote IPC " Anatoly Burakov
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 2/7] fbarray: promote " Anatoly Burakov
2021-09-10 15:52   ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 3/7] eal: promote malloc " Anatoly Burakov
2021-09-10 15:53   ` Kinsella, Ray [this message]
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 4/7] mem: promote memseg " Anatoly Burakov
2021-09-10 15:55   ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 5/7] mem: promote extmem " Anatoly Burakov
2021-09-10 15:56   ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 6/7] mem: promote DMA mask " Anatoly Burakov
2021-09-10 15:56   ` Kinsella, Ray
2021-09-10 12:30 ` [dpdk-dev] [PATCH v1 7/7] eal: promote mcfg " Anatoly Burakov
2021-09-10 16:23   ` Kinsella, Ray
2021-09-10 15:51 ` [dpdk-dev] [PATCH v1 1/7] eal: promote IPC " Kinsella, Ray
2021-09-29  5:48   ` 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=30ebe2a8-f555-6ecc-6853-968fcac1c843@ashroe.eu \
    --to=mdr@ashroe.eu \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.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).