On Tue, Jan 24, 2023 at 7:12 PM Tyler Retzlaff <roret...@linux.microsoft.com> wrote: > > v10: > * change intended deprecation of rte_thread_setname > from 23.03 to 23.07 > > v9: > * fix typo in v8 deprecation notice picked up by ci > > v8: > * document that no implementation or internal implementation > failure is a noop for rte_thread_set_name > * update commit message to indicate windows now provides an > implementation for rte_thread_set_name > * remove '_' from thread_name in comment > * squish drivers/mlx5 patch into patch 1 as requested > * clarify rte_thread_setname anticipated deprecation and removal > releases in deprecation notice > * group deprecation notice with other eal deprecation notices > > v7: > * don't dereference thread_name after successful completion > of mbsrtowcs. (fixes NULL dereference on Windows). > > v6: > * clean up commit descriptions > * add patch to set worker thread name on windows > * remove __rte_deprecated from rte_thread_setname > > v5: > * rename rte_thread_getname -> thread_get_name > > v4: > * retain and move rte_thread_getname function to the > single site of use > > v3: > * fix coding style error > * move remove of rte_thread_getname to patch #2 > > v2: > * initial series provided get/set for lcore thread id, those > additions have been removed as per discussion. including > unit test > * add a single api rte_thread_set_name does not fail but emits > debug logging if the internal implementation is aware of > in-exact use of the name or failure to set the name > * adapt mlx5 driver to avoid use of deprecated API
Series applied, thanks Tyler. -- David Marchand
