From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] malloc: deprecate unused set limit
Date: Thu, 27 Jun 2019 09:09:09 +0100 [thread overview]
Message-ID: <8fc8f114-187d-96c9-52c4-680e3dcbe868@intel.com> (raw)
In-Reply-To: <20190626223212.25815-1-stephen@networkplumber.org>
On 26-Jun-19 11:32 PM, Stephen Hemminger wrote:
> The function rte_malloc_set_limit was defined but never implemented.
> Mark it as deprecated for now, and remove in next release.
>
> There is no point in keeping dead code.
> "You Aren't Going to Need It"
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
--
Thanks,
Anatoly
next prev parent reply other threads:[~2019-06-27 8:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-26 22:32 [dpdk-dev] [PATCH] malloc: deprecate unused set limit Stephen Hemminger
2019-06-27 8:09 ` Burakov, Anatoly [this message]
2019-07-01 16:37 ` Thomas Monjalon
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=8fc8f114-187d-96c9-52c4-680e3dcbe868@intel.com \
--to=anatoly.burakov@intel.com \
--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).