Notify deprecation of rte_ctrl_thread_create API, it will be removed as it exposes platform-specific thread details.
Signed-off-by: Tyler Retzlaff <roret...@linux.microsoft.com> Acked-by: Morten Brørup <m...@smartsharesystems.com> Acked-by: David Marchand <david.march...@redhat.com> Reviewed-by: Mattias Rönnblom <mattias.ronnb...@ericsson.com> --- doc/guides/rel_notes/deprecation.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst index ac9aa76..6eb9721 100644 --- a/doc/guides/rel_notes/deprecation.rst +++ b/doc/guides/rel_notes/deprecation.rst @@ -23,10 +23,10 @@ Deprecation Notices in the future. Applications can use ``devtools/cocci/func_or_ret.cocci`` to update their code. -* eal: The function ``rte_thread_setname`` is planned to be deprecated - starting with the 23.07 release, subject to the replacement API - rte_thread_set_name being marked as stable, and planned to be removed - by the 23.11 release. +* eal: The function ``rte_thread_setname`` and ``rte_ctrl_thread_create`` + are planned to be deprecated starting with the 23.07 release, subject to + the replacement API rte_thread_set_name and rte_thread_create_control being + marked as stable, and planned to be removed by the 23.11 release. * rte_atomicNN_xxx: These APIs do not take memory order parameter. This does not allow for writing optimized code for all the CPU architectures supported -- 1.8.3.1
