From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id A55B8440B6; Fri, 24 May 2024 17:43:35 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 2FEAF4068A; Fri, 24 May 2024 17:43:35 +0200 (CEST) Received: from wfout3-smtp.messagingengine.com (wfout3-smtp.messagingengine.com [64.147.123.146]) by mails.dpdk.org (Postfix) with ESMTP id CFA494068A for ; Fri, 24 May 2024 17:43:33 +0200 (CEST) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailfout.west.internal (Postfix) with ESMTP id E58C81C0010A; Fri, 24 May 2024 11:43:29 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Fri, 24 May 2024 11:43:30 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:cc:content-transfer-encoding:content-type:content-type:date :date:from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm1; t=1716565409; x=1716651809; bh=5/lWANUYT+/dxkiuAlkyOL2Mc2I9cDedFpu+fgPi7FM=; b= vzJFTB/gNArw3k11OGhwJeQMG0/hpg94aZ76ck/ru3Vo/RA0H2i7l0rjprR/rGFq V8XRsZWsoMjJpLsSFbtqUWe/0KrBbCE+DAB+til0ResFy2qGSqEIbJugz9/4259N UdAEOaHNEWNprB0tm3rtmM60mUCDGNoe0a8+lb8xGG8h3aqkhFRvKtlP7a2Ufy1A t4OVjgjhQB036MiSQx39vm9heV8ZOxOpTzDAFY9wbkbLP/IdIQ2Y5Dm+hO7if2L7 GKeKgma8jgpdXPX1VEV7sQywm9aeYrcs5IZcfhQ5z2S6RKvdcq5a3BK4cE56af/9 n7HgV/ysNwR0sHCbTi8QKw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1716565409; x= 1716651809; bh=5/lWANUYT+/dxkiuAlkyOL2Mc2I9cDedFpu+fgPi7FM=; b=k ShlWN5uPVIs2q2hCgc/bsKowyGBUW/h0ZRvgW3llGZnm7eGIDc/smcULUey+Kg4S C3EzinmoHYJKd37Zw2mL8h3l0bxZwpOscb7NNiDOT6kRoEQo18I1VLVhGvCQ6qT5 dy+bw/5YtcqbvIXC3Mqgwi8IbrNe22gudt6TQMeDIyjRtLg73kE72/uYJAds2y4f kyYdSAIGXmks/21AJaIoGDydJTL/izQqVVg6L2Hz31xa2LkNdltYrh3xpv0OU1+F ccri2nBaJSJL/fUWl6FArp/niLJV0ETrgUusYyCicq5jnlGZwHrjzXHSYMG6Gahu MW1RbUNwSVnllQHQSx3ag== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvdeikedgkeelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephffvvefufffkjghfggfgtgesthfuredttddtjeenucfhrhhomhepvfhhohhm rghsucfoohhnjhgrlhhonhcuoehthhhomhgrshesmhhonhhjrghlohhnrdhnvghtqeenuc ggtffrrghtthgvrhhnpeetvddvuefhteffhfejgeffvdduiedvffelueekteeuudfhudeh leffleejjeeutdenucffohhmrghinhepnhhvihguihgrrdgtohhmnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepthhhohhmrghssehmohhnjhgr lhhonhdrnhgvth X-ME-Proxy: Feedback-ID: i47234305:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 24 May 2024 11:43:28 -0400 (EDT) From: Thomas Monjalon To: Dariusz Sosnowski Cc: "dev@dpdk.org" , Slava Ovsiienko , Ori Kam , Suanming Mou , Matan Azrad Subject: Re: [PATCH] doc: add firmware update links in mlx5 guide Date: Fri, 24 May 2024 17:43:25 +0200 Message-ID: <1986979.jZfb76A358@thomas> In-Reply-To: References: <20240523112850.1446671-1-thomas@monjalon.net> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="utf-8" X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org 24/05/2024 17:36, Dariusz Sosnowski: > > +The firmware can be updated with `mlxup > > +`_. > > +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.