From: Thomas Monjalon <thomas@monjalon.net>
To: Zhiheng Chen <chenzhiheng0227@gmail.com>
Cc: Matan Azrad <matan@nvidia.com>,
Viacheslav Ovsiienko <viacheslavo@nvidia.com>,
dev@dpdk.org
Subject: Re: [PATCH] doc: update Mellanox drivers download link in mlx5 guide
Date: Sun, 27 Feb 2022 12:46:02 +0100 [thread overview]
Message-ID: <4785240.mvXUDI8C0e@thomas> (raw)
In-Reply-To: <20220226034800.16052-1-chenzhiheng0227@gmail.com>
26/02/2022 04:48, Zhiheng Chen:
> The original download link is invalid.
>
> Signed-off-by: Zhiheng Chen <chenzhiheng0227@gmail.com>
> ---
> doc/guides/nics/mlx5.rst | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/doc/guides/nics/mlx5.rst b/doc/guides/nics/mlx5.rst
> index c3cc0c0f41..625d8a2382 100644
> --- a/doc/guides/nics/mlx5.rst
> +++ b/doc/guides/nics/mlx5.rst
> @@ -1385,9 +1385,9 @@ managers on most distributions, this PMD requires Ethernet extensions that
> may not be supported at the moment (this is a work in progress).
>
> `Mellanox OFED
> -<http://www.mellanox.com/page/products_dyn?product_family=26&mtag=linux>`__ and
> +<https://network.nvidia.com/products/infiniband-drivers/linux/mlnx_ofed/>`__ and
> `Mellanox EN
> -<http://www.mellanox.com/page/products_dyn?product_family=27&mtag=linux>`__
> +<https://network.nvidia.com/products/ethernet-drivers/linux/mlnx_en/>`__
> include the necessary support and should be used in the meantime. For DPDK,
> only libibverbs, libmlx5, mlnx-ofed-kernel packages and firmware updates are
> required from that distribution.
This patch will be mark as non-applicable because it is already fixed
by this patch:
https://patches.dpdk.org/project/dpdk/patch/20220223134834.2840916-3-michaelba@nvidia.com/
Thank you anyway
prev parent reply other threads:[~2022-02-27 11:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-26 3:48 [PATCH] doc: update Mellanox drivers download link in mlx5 guide Zhiheng Chen
2022-02-27 11:46 ` Thomas Monjalon [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4785240.mvXUDI8C0e@thomas \
--to=thomas@monjalon.net \
--cc=chenzhiheng0227@gmail.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=viacheslavo@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.