From: Andrew Lunn <andrew@lunn.ch>
To: Suman Ghosh <sumang@marvell.com>
Cc: Sunil Kovvuri Goutham <sgoutham@marvell.com>,
Geethasowjanya Akula <gakula@marvell.com>,
Subbaraya Sundeep Bhatta <sbhatta@marvell.com>,
Hariprasad Kelam <hkelam@marvell.com>,
Linu Cherian <lcherian@marvell.com>,
Jerin Jacob Kollanukkaran <jerinj@marvell.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"horms@kernel.org" <horms@kernel.org>,
Ratheesh Kannoth <rkannoth@marvell.com>
Subject: Re: [EXT] Re: [net PATCH] octeontx2: Fix klockwork and coverity issues
Date: Fri, 3 Nov 2023 18:06:08 +0100 [thread overview]
Message-ID: <bafea4cc-9bf9-4485-a85b-206b82e0b21c@lunn.ch> (raw)
In-Reply-To: <SJ0PR18MB521648A973DF026521B57D39DBA5A@SJ0PR18MB5216.namprd18.prod.outlook.com>
> [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
next prev parent reply other threads:[~2023-11-03 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 7:49 Suman Ghosh
2023-11-01 12:42 ` Andrew Lunn
2023-11-03 16:39 ` [EXT] " Suman Ghosh
2023-11-03 17:06 ` Andrew Lunn [this message]
2023-11-14 5:23 ` Suman Ghosh
2023-11-14 16:42 ` Christophe JAILLET
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=bafea4cc-9bf9-4485-a85b-206b82e0b21c@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=sbhatta@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@marvell.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
all inboxes | Powered by JetHome®