[PATCH] doc: remove Mellanox acquisition explanation

[PATCH] doc: remove Mellanox acquisition explanation

[Thomas Monjalon]

Time has passed since Mellanox acquisition by NVIDIA.
No need to explain this anymore.

Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
 doc/guides/compressdevs/mlx5.rst  | 7 -------
 doc/guides/cryptodevs/mlx5.rst    | 7 -------
 doc/guides/nics/mlx4.rst          | 7 -------
 doc/guides/nics/mlx5.rst          | 6 ------
 doc/guides/platform/bluefield.rst | 7 -------
 doc/guides/platform/mlx5.rst      | 7 -------
 doc/guides/regexdevs/mlx5.rst     | 7 -------
 doc/guides/vdpadevs/mlx5.rst      | 7 -------
 8 files changed, 55 deletions(-)

diff --git a/doc/guides/compressdevs/mlx5.rst b/doc/guides/compressdevs/mlx5.rst
index 751fae7184..b64818444a 100644
--- a/doc/guides/compressdevs/mlx5.rst
+++ b/doc/guides/compressdevs/mlx5.rst
@@ -6,13 +6,6 @@
 NVIDIA MLX5 Compress Driver
 ===========================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 The mlx5 compress driver library
 (**librte_compress_mlx5**) provides support for **NVIDIA BlueField-2**,
 and **NVIDIA BlueField-3** families of 25/50/100/200/400 Gb/s adapters.
diff --git a/doc/guides/cryptodevs/mlx5.rst b/doc/guides/cryptodevs/mlx5.rst
index f8b43823a7..8a2ec20e74 100644
--- a/doc/guides/cryptodevs/mlx5.rst
+++ b/doc/guides/cryptodevs/mlx5.rst
@@ -6,13 +6,6 @@
 NVIDIA MLX5 Crypto Driver
 =========================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 The MLX5 crypto driver library
 (**librte_crypto_mlx5**) provides support for **NVIDIA ConnectX-6**,
 **NVIDIA ConnectX-6 Dx**, **NVIDIA ConnectX-7**, **NVIDIA ConnectX-8**,
diff --git a/doc/guides/nics/mlx4.rst b/doc/guides/nics/mlx4.rst
index d79d5b1661..e92fcc155c 100644
--- a/doc/guides/nics/mlx4.rst
+++ b/doc/guides/nics/mlx4.rst
@@ -5,13 +5,6 @@
 NVIDIA MLX4 Ethernet Driver
 ===========================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 The MLX4 poll mode driver library (**librte_net_mlx4**) implements support
 for **NVIDIA ConnectX-3** and **NVIDIA ConnectX-3 Pro** 10/40 Gbps adapters
 as well as their virtual functions (VF) in SR-IOV context.
diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
index c3a350d24e..5c825dd6b0 100644
--- a/doc/guides/nics/mlx5.rst
+++ b/doc/guides/nics/mlx5.rst
@@ -7,12 +7,6 @@
 NVIDIA MLX5 Ethernet Driver
 ===========================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
 
 The mlx5 Ethernet poll mode driver library (**librte_net_mlx5**) provides support
 for **NVIDIA ConnectX-4**, **NVIDIA ConnectX-4 Lx** , **NVIDIA ConnectX-5**,
diff --git a/doc/guides/platform/bluefield.rst b/doc/guides/platform/bluefield.rst
index a568cdca4c..67a70b1313 100644
--- a/doc/guides/platform/bluefield.rst
+++ b/doc/guides/platform/bluefield.rst
@@ -4,13 +4,6 @@
 NVIDIA BlueField Board Support Package
 ======================================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 This document has information about steps to setup NVIDIA BlueField platform
 and common offload HW drivers of **NVIDIA BlueField** family SoC.
 
diff --git a/doc/guides/platform/mlx5.rst b/doc/guides/platform/mlx5.rst
index ab3107209a..8742f84972 100644
--- a/doc/guides/platform/mlx5.rst
+++ b/doc/guides/platform/mlx5.rst
@@ -7,13 +7,6 @@
 NVIDIA MLX5 Common Driver
 =========================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 The mlx5 common driver library (**librte_common_mlx5**) provides support for
 **NVIDIA ConnectX-4**, **NVIDIA ConnectX-4 Lx**, **NVIDIA ConnectX-5**,
 **NVIDIA ConnectX-6**, **NVIDIA ConnectX-6 Dx**, **NVIDIA ConnectX-6 Lx**,
diff --git a/doc/guides/regexdevs/mlx5.rst b/doc/guides/regexdevs/mlx5.rst
index 174b848158..814228c5e3 100644
--- a/doc/guides/regexdevs/mlx5.rst
+++ b/doc/guides/regexdevs/mlx5.rst
@@ -6,13 +6,6 @@
 NVIDIA MLX5 RegEx Driver
 ========================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 The mlx5 RegEx (Regular Expression) driver library
 (**librte_regex_mlx5**) provides support for **NVIDIA BlueField-2**,
 and **NVIDIA BlueField-3** families of 25/50/100/200 Gb/s adapters.
diff --git a/doc/guides/vdpadevs/mlx5.rst b/doc/guides/vdpadevs/mlx5.rst
index f6c3068a21..e7d37aa4ea 100644
--- a/doc/guides/vdpadevs/mlx5.rst
+++ b/doc/guides/vdpadevs/mlx5.rst
@@ -6,13 +6,6 @@
 NVIDIA MLX5 vDPA Driver
 =======================
 
-.. note::
-
-   NVIDIA acquired Mellanox Technologies in 2020.
-   The DPDK documentation and code might still include instances
-   of or references to Mellanox trademarks (like BlueField and ConnectX)
-   that are now NVIDIA trademarks.
-
 The mlx5 vDPA (vhost data path acceleration) driver library
 (**librte_vdpa_mlx5**) provides support for **NVIDIA ConnectX-6**,
 **NVIDIA ConnectX-6 Dx**, **NVIDIA ConnectX-6 Lx**, **NVIDIA ConnectX7**,
-- 
2.47.1

Re: [PATCH] doc: remove Mellanox acquisition explanation

[Bruce Richardson]

On Wed, Jul 16, 2025 at 12:15:16PM +0200, Thomas Monjalon wrote:
> Time has passed since Mellanox acquisition by NVIDIA.
> No need to explain this anymore.
> 
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---

I wonder if we should include in DPDK a "future_cleanups" doc which
describes cleanups that can or should be done at specific points. For
example, after a specific release or date, or after we drop support for a
compiler or kernel version. After we add a workaround for a particular
tooling issue (or other change), it would be nice to have somewhere to
record when exactly the workaround can be removed and how/why to do so.

/Bruce

Re: [PATCH] doc: remove Mellanox acquisition explanation

[Thomas Monjalon]

16/07/2025 12:37, Bruce Richardson:
> On Wed, Jul 16, 2025 at 12:15:16PM +0200, Thomas Monjalon wrote:
> > Time has passed since Mellanox acquisition by NVIDIA.
> > No need to explain this anymore.
> > 
> > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > ---
> 
> I wonder if we should include in DPDK a "future_cleanups" doc which
> describes cleanups that can or should be done at specific points. For
> example, after a specific release or date, or after we drop support for a
> compiler or kernel version. After we add a workaround for a particular
> tooling issue (or other change), it would be nice to have somewhere to
> record when exactly the workaround can be removed and how/why to do so.

It looks very programmatic :)
Yes why not.

In this case, there was no clear deadline.

Re: [PATCH] doc: remove Mellanox acquisition explanation

[Stephen Hemminger]

On Wed, 16 Jul 2025 17:56:04 +0200
Thomas Monjalon <thomas@monjalon.net> wrote:

> 16/07/2025 12:37, Bruce Richardson:
> > On Wed, Jul 16, 2025 at 12:15:16PM +0200, Thomas Monjalon wrote:  
> > > Time has passed since Mellanox acquisition by NVIDIA.
> > > No need to explain this anymore.
> > > 
> > > Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> > > ---  
> > 
> > I wonder if we should include in DPDK a "future_cleanups" doc which
> > describes cleanups that can or should be done at specific points. For
> > example, after a specific release or date, or after we drop support for a
> > compiler or kernel version. After we add a workaround for a particular
> > tooling issue (or other change), it would be nice to have somewhere to
> > record when exactly the workaround can be removed and how/why to do so.  
> 
> It looks very programmatic :)
> Yes why not.
> 
> In this case, there was no clear deadline.
> 
> 

There still are lots of experimental API's to make stable as well.