From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id BAB6EC43460 for ; Wed, 28 Apr 2021 14:19:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8599B61412 for ; Wed, 28 Apr 2021 14:19:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S240249AbhD1OTr (ORCPT ); Wed, 28 Apr 2021 10:19:47 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:44582 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230050AbhD1OTn (ORCPT ); Wed, 28 Apr 2021 10:19:43 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1lbl1g-001WIT-Dq; Wed, 28 Apr 2021 16:18:52 +0200 Date: Wed, 28 Apr 2021 16:18:52 +0200 From: Andrew Lunn To: Vadym Kochan Cc: "David S. Miller" , Jakub Kicinski , netdev@vger.kernel.org, Taras Chornyi , linux-kernel@vger.kernel.org, Mickey Rachamim , Vadym Kochan Subject: Re: [PATCH net-next 1/3] net: marvell: prestera: bump supported firmware version to 3.0 Message-ID: References: <20210423155933.29787-1-vadym.kochan@plvision.eu> <20210423155933.29787-2-vadym.kochan@plvision.eu> <20210423170437.GC17656@plvision.eu> <20210428134724.GA405@plvision.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210428134724.GA405@plvision.eu> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Regarding the distribution issue when the driver version might be released > earlier than the firmware, it looks like that the probability of such > case is very low because the distributor of the target Linux system will > keep track (actually this is how I see it) that driver and firmware > versions are aligned. You really expect Debian, Redhat, openWRT, SuSE to keep a close eye on your kernel driver and update their packages at a time you suggest? I'm also not sure your management port argument is valid. This is an enterprise switch, not a TOR. It is probably installed in some broom cupboard at a satellite facility. The management port is not likely to have its own dedicated link back to the central management site. Upgrades are going to be applied over the network, and you have a real danger of turning it into a remote brick, needing local access to restore it. I really think you need to support two firmware generations. Andrew