From: Andrew Rybchenko <arybchenko@solarflare.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "thomas@monjalon.net" <thomas@monjalon.net>,
"aconole@redhat.com" <aconole@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] doc: announce cpuflags check symbol removal
Date: Tue, 6 Aug 2019 16:56:01 +0300 [thread overview]
Message-ID: <096f6d7b-1836-73e5-e231-57d58e70c661@solarflare.com> (raw)
In-Reply-To: <2601191342CEEE43887BDE71AB9772580168A629FD@irsmsx105.ger.corp.intel.com>
On 8/6/19 4:54 PM, Ananyev, Konstantin wrote:
>
>
>> 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>
>> ---
>> doc/guides/rel_notes/deprecation.rst | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
>> index 37b8592..58b1852 100644
>> --- a/doc/guides/rel_notes/deprecation.rst
>> +++ b/doc/guides/rel_notes/deprecation.rst
>> @@ -34,6 +34,9 @@ Deprecation Notices
>>
>> + ``rte_eal_devargs_type_count``
>>
>> +* eal: The ``rte_cpu_check_supported`` function has been deprecated since
>> + v17.08 and will be removed in DPDK 19.11.
>> +
>> * vfio: removal of ``rte_vfio_dma_map`` and ``rte_vfio_dma_unmap`` APIs which
>> have been replaced with ``rte_dev_dma_map`` and ``rte_dev_dma_unmap``
>> functions. The due date for the removal targets DPDK 20.02.
>> --
>
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
Acked-by: Andrew Rybchenko <arybchenko@solarflare.com>
next prev parent reply other threads:[~2019-08-06 13:56 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
2019-08-06 13:54 ` Ananyev, Konstantin
2019-08-06 13:56 ` Andrew Rybchenko [this message]
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=096f6d7b-1836-73e5-e231-57d58e70c661@solarflare.com \
--to=arybchenko@solarflare.com \
--cc=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.com \
--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).