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 Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id B14D1C4332F for ; Fri, 3 Nov 2023 17:06:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1376665AbjKCRG2 (ORCPT ); Fri, 3 Nov 2023 13:06:28 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49240 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1345483AbjKCRGZ (ORCPT ); Fri, 3 Nov 2023 13:06:25 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E8EA4D47; Fri, 3 Nov 2023 10:06:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=zceykpx/VhpqN1zRb1lvrV0ipA+xbJD7LJTS3nOqa80=; b=vm9C2bhQR1dTP96MoYHCSqw2HI 9CyvuRDnDaHdB1dlqTbSrfS0Ma9rtBnj4J1g03waAew+KhWboI35fnY3asv7byH8Ed89ZIKBu3eC7 9DxARIHREFWkcEEKe33qz83GQSAZfptSMwJnag+cRFpMMjBcvEqAyid38qIHNToC0JnE=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1qyxcW-000peM-Vr; Fri, 03 Nov 2023 18:06:08 +0100 Date: Fri, 3 Nov 2023 18:06:08 +0100 From: Andrew Lunn To: Suman Ghosh Cc: Sunil Kovvuri Goutham , Geethasowjanya Akula , Subbaraya Sundeep Bhatta , Hariprasad Kelam , Linu Cherian , Jerin Jacob Kollanukkaran , "davem@davemloft.net" , "edumazet@google.com" , "kuba@kernel.org" , "pabeni@redhat.com" , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "horms@kernel.org" , Ratheesh Kannoth Subject: Re: [EXT] Re: [net PATCH] octeontx2: Fix klockwork and coverity issues Message-ID: References: <20231101074919.2614608-1-sumang@marvell.com> <335216cc-3412-4898-8b88-10405ff7c316@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > [Suman] Yes, backporting to net was the intention. Do we need to put all the fixes tags? Because the fixes are from different commits. When you break it up into multiple patches, the fixes-tag will get simpler. > Are there any generic submission steps for klockwork fixes? Take a look at https://docs.kernel.org/process/stable-kernel-rules.html In particular, the "It must fix a real bug that bothers people". Some issues found by static code tools don't actually bother people. So you might want some patches to net-next, not net. Andrew