From: Aaron Conole <aconole@redhat.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, thomas@monjalon.net
Subject: Re: [dpdk-dev] [PATCH] doc: announce cpuflags check symbol removal
Date: Fri, 26 Jul 2019 09:40:28 -0400 [thread overview]
Message-ID: <f7twog4gbhv.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <1564129654-9161-1-git-send-email-david.marchand@redhat.com> (David Marchand's message of "Fri, 26 Jul 2019 10:27:34 +0200")
David Marchand <david.marchand@redhat.com> writes:
> This symbol has been deprecated for quite some time.
> Let's drop it in the next release.
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
I don't know how many out-of-tree users there are. OVS doesn't use this
symbol - and a brief look at github (first 25 pages of results) shows
that it's all clones of DPDK, 1 rust autogenerated FFI, and 1 "nimble"
autogenerated FFI.
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2019-07-26 13:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 8:27 David Marchand
2019-07-26 13:40 ` Aaron Conole [this message]
2019-08-06 13:54 ` Ananyev, Konstantin
2019-08-06 13:56 ` Andrew Rybchenko
2019-08-08 9:30 ` [dpdk-dev] [PATCH v2] " David Marchand
2019-08-08 10:07 ` Jerin Jacob Kollanukkaran
2019-08-08 11:51 ` 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=f7twog4gbhv.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).