[dpdk-dev v1] doc: update Multi-buffer library version to 2.0.1

[Bruce Richardson]

On Mon, Mar 02, 2026 at 04:47:42PM +0000, Kai Ji wrote:
> Update the maximum supported Intel Multi-buffer library version
> from 1.5 to 2.0.1 for DPDK 24.11+ in the cryptodev guides.
> 
> Signed-off-by: Kai Ji <kai.ji at intel.com>
> ---
>  doc/guides/cryptodevs/aesni_gcm.rst         | 2 +-
>  doc/guides/cryptodevs/aesni_mb.rst          | 2 +-
>  doc/guides/cryptodevs/chacha20_poly1305.rst | 2 +-
>  doc/guides/cryptodevs/snow3g.rst            | 2 +-
>  doc/guides/cryptodevs/zuc.rst               | 2 +-
>  5 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/doc/guides/cryptodevs/aesni_gcm.rst b/doc/guides/cryptodevs/aesni_gcm.rst
> index 16bdaf3cb4..8d833c92aa 100644
> --- a/doc/guides/cryptodevs/aesni_gcm.rst
> +++ b/doc/guides/cryptodevs/aesni_gcm.rst
> @@ -75,7 +75,7 @@ and the external crypto libraries supported by them:
>     =============  ================================
>     20.11 - 21.08  Multi-buffer library 0.53 - 1.3
>     21.11 - 24.07  Multi-buffer library 1.0  - 1.5
> -   24.11+         Multi-buffer library 1.4  - 1.5
> +   24.11+         Multi-buffer library 1.4  - 2.0.1
>     =============  ================================
>  

Minor question - is it worth leaving the last version here as open ended
until such time as you get a version that is not supported in that release,
e.g. "24.11+ Multi-buffer library 1.4+"?

That would save updating each time there is a new supported release, and
you can close off the line and start a new one once there is a release you
don't support for that version any longer..

/Bruce