From: David Marchand <david.marchand@6wind.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: Olivier Matz <olivier.matz@6wind.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] remove poisoned flags
Date: Wed, 20 Apr 2016 10:59:32 +0200 [thread overview]
Message-ID: <CALwxeUvNRa=Gs-J2gniv4ngGNgL8EK2s1G5TET7mOfp3Rn+5+Q@mail.gmail.com> (raw)
In-Reply-To: <1461097157-28925-1-git-send-email-thomas.monjalon@6wind.com>
On Tue, Apr 19, 2016 at 10:19 PM, Thomas Monjalon
<thomas.monjalon@6wind.com> wrote:
> Some flags were poisoned after having been removed from EAL and mbuf
> in releases 1.8 (b10eef348d, 62814bc2e9) and 2.0 (4769bc5a27cc).
> After several releases, they have probably disappeared from the applications.
>
> 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-04-20 8:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 20:19 Thomas Monjalon
2016-04-20 8:59 ` David Marchand [this message]
2016-04-22 13:56 ` 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='CALwxeUvNRa=Gs-J2gniv4ngGNgL8EK2s1G5TET7mOfp3Rn+5+Q@mail.gmail.com' \
--to=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--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).