From: Thomas Monjalon
> There is a layer violation in the vDPA API for getting the device name.
> Instead of providing the name at vDPA level, a function returns the low-level
> device object.
> The plan is to introduce a new function in 22.11, promote in 23.07, and remove
> rte_vdpa_get_rte_device() in 23.11.
>
> Signed-off-by: Thomas Monjalon <tho...@monjalon.net>
> ---
> v2: one year passed, update with a new plan
> v1 was proposing a close function, only device name is needed
> ---
> doc/guides/rel_notes/deprecation.rst | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/doc/guides/rel_notes/deprecation.rst
> b/doc/guides/rel_notes/deprecation.rst
> index 4e5b23c53d..0f7fefbf6a 100644
> --- a/doc/guides/rel_notes/deprecation.rst
> +++ b/doc/guides/rel_notes/deprecation.rst
> @@ -107,6 +107,13 @@ Deprecation Notices
> alternative is implemented.
> The legacy actions should be removed in DPDK 22.11.
>
> +* vdpa: The vDPA API should not try to manipulate or export
> + any ``rte_device`` object, which belongs to the bus layer.
> + The function ``rte_vdpa_get_rte_device()`` will be deprecated in
> +23.07,
> + when its usage will be replaced with ``rte_vdpa_get_device_name()``.
> + The new function should enter in 22.11 and get promoted to stable in 23.07.
> + The target is to remove ``rte_vdpa_get_rte_device()`` in 23.11.
> +
> * cryptodev: Hide structures ``rte_cryptodev_sym_session`` and
> ``rte_cryptodev_asym_session`` to remove unnecessary indirection between
> session and the private data of session. An opaque pointer can be exposed
> --
> 2.36.1
Acked-by: Matan Azrad <ma...@nvidia.com>
