doc: remove unneeded min/max fields deprecations
It was announced that `min` and `max` fields and variables in public headers will be renamed to avoid clash with `min` and `max` macros defined in Windows headers. However, it is unnecessary, because these are function-like macros, which are not expanded unless the next token is an opening brace. It cannot happen for integer fields and variables. Remove the deprecation notices. Fixes: c4379ee599ef ("doc: announce API changes for Windows compatibility") Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
This commit is contained in:
parent
04d43857ea
commit
515d20195b
@ -185,12 +185,6 @@ Deprecation Notices
|
||||
and ``rte_vhost_driver_set_protocol_features`` functions will be removed
|
||||
and the API functions will be made stable in DPDK 21.11.
|
||||
|
||||
* compressdev: ``min`` and ``max`` fields of ``rte_param_log2_range`` structure
|
||||
will be renamed in DPDK 21.11 to avoid conflict with Windows Sockets headers.
|
||||
|
||||
* cryptodev: ``min`` and ``max`` fields of ``rte_crypto_param_range`` structure
|
||||
will be renamed in DPDK 21.11 to avoid conflict with Windows Sockets headers.
|
||||
|
||||
* cryptodev: The field ``dataunit_len`` of the ``struct rte_crypto_cipher_xform``
|
||||
has a limited size ``uint16_t``.
|
||||
It will be moved and extended as ``uint32_t`` in DPDK 21.11.
|
||||
|
Loading…
x
Reference in New Issue
Block a user