From: David Marchand <david.marchand@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v3] log: deprecate history dump
Date: Fri, 10 Jun 2016 11:50:10 +0200 [thread overview]
Message-ID: <CALwxeUugjQFX8=pv1SBEPDBw0W0gGH7rB8E0chXSZ2g84AZejQ@mail.gmail.com> (raw)
In-Reply-To: <1465510241-21417-1-git-send-email-thomas.monjalon@6wind.com>
On Fri, Jun 10, 2016 at 12:10 AM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> The log history uses rte_mempool. In order to remove the mempool
> dependency in EAL (and improve the build), this feature is deprecated.
> The ABI is kept but the behaviour is now voided because it seems this
> function was not used. The history can be read from syslog.
>
> Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
Acked-by: David Marchand <david.marchand@6wind.com>
--
David Marchand
next prev parent reply other threads:[~2016-06-10 9:50 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 14:09 [dpdk-dev] [PATCH] " Thomas Monjalon
2016-06-09 14:45 ` David Marchand
2016-06-09 15:01 ` Thomas Monjalon
2016-06-09 21:26 ` [dpdk-dev] [PATCH] dropping librte_ivshmem - was " Thomas Monjalon
2016-06-10 9:05 ` Burakov, Anatoly
2016-06-10 9:30 ` Thomas Monjalon
2016-06-10 9:47 ` Burakov, Anatoly
2016-06-10 10:13 ` Thomas Monjalon
2016-06-10 12:08 ` Burakov, Anatoly
2016-06-10 12:26 ` Thomas Monjalon
2016-06-15 18:16 ` Ferruh Yigit
2016-06-15 18:34 ` [dpdk-dev] [PATCH] dropping librte_ivshmem Thomas Monjalon
2016-06-20 15:44 ` Ferruh Yigit
2016-06-20 15:54 ` Thomas Monjalon
2016-06-21 6:49 ` [dpdk-dev] [PATCH] dropping librte_ivshmem - was log: deprecate history dump Panu Matilainen
2016-06-09 15:01 ` [dpdk-dev] [PATCH] " Christian Ehrhardt
2016-06-09 15:06 ` [dpdk-dev] [PATCH v2] " Thomas Monjalon
2016-06-09 22:10 ` [dpdk-dev] [PATCH v3] " Thomas Monjalon
2016-06-10 9:50 ` David Marchand [this message]
2016-06-10 13:09 ` 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='CALwxeUugjQFX8=pv1SBEPDBw0W0gGH7rB8E0chXSZ2g84AZejQ@mail.gmail.com' \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).