From: Dariusz Sosnowski <dsosnowski@nvidia.com>
To: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Ori Kam <orika@nvidia.com>, Suanming Mou <suanmingm@nvidia.com>,
Matan Azrad <matan@nvidia.com>
Subject: RE: [PATCH] doc: add firmware update links in mlx5 guide
Date: Fri, 24 May 2024 15:56:13 +0000 [thread overview]
Message-ID: <PH0PR12MB880088F2F54D4F1424E015BEA4F52@PH0PR12MB8800.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1986979.jZfb76A358@thomas>
> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, May 24, 2024 17:43
> To: Dariusz Sosnowski <dsosnowski@nvidia.com>
> Cc: dev@dpdk.org; Slava Ovsiienko <viacheslavo@nvidia.com>; Ori Kam
> <orika@nvidia.com>; Suanming Mou <suanmingm@nvidia.com>; Matan Azrad
> <matan@nvidia.com>
> Subject: Re: [PATCH] doc: add firmware update links in mlx5 guide
>
> 24/05/2024 17:36, Dariusz Sosnowski:
> > > +The firmware can be updated with `mlxup
> > > +<https://docs.nvidia.com/networking/display/mlxupfwutility>`_.
> > > +The latest firmwares can be downloaded at
> > > +https://network.nvidia.com/support/firmware/firmware-downloads/
> > > +
> >
> > What do you think about moving these lines from "Upstream dependencies" to
> after:
> >
> > "+ New features may be added in more recent firmwares."
> >
> > in firmware subsection?
> >
> > I don't think that "Upstream dependencies" is a good place for this info.
>
> mlxup is downloaded separately only in case of upstream dependencies.
> If using MLNX_OFED, firmware tools are included, so it would be redundant.
Ok, makes sense. Thank you.
Acked-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
Best regards,
Dariusz Sosnowski
next prev parent reply other threads:[~2024-05-24 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 11:28 Thomas Monjalon
2024-05-24 15:36 ` Dariusz Sosnowski
2024-05-24 15:43 ` Thomas Monjalon
2024-05-24 15:56 ` Dariusz Sosnowski [this message]
2024-05-27 11:40 ` Raslan Darawsheh
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=PH0PR12MB880088F2F54D4F1424E015BEA4F52@PH0PR12MB8800.namprd12.prod.outlook.com \
--to=dsosnowski@nvidia.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=suanmingm@nvidia.com \
--cc=thomas@monjalon.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).