[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <335216cc-3412-4898-8b88-10405ff7c316@lunn.ch>
Date: Wed, 1 Nov 2023 13:42:24 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Suman Ghosh <sumang@...vell.com>
Cc: sgoutham@...vell.com, gakula@...vell.com, sbhatta@...vell.com,
hkelam@...vell.com, lcherian@...vell.com, jerinj@...vell.com,
davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, horms@...nel.org,
Ratheesh Kannoth <rkannoth@...vell.com>
Subject: Re: [net PATCH] octeontx2: Fix klockwork and coverity issues
On Wed, Nov 01, 2023 at 01:19:19PM +0530, Suman Ghosh wrote:
> Fix all klockwork and coverity issues reported on AF and PF/VF driver.
>
> Signed-off-by: Suman Ghosh <sumang@...vell.com>
> Signed-off-by: Ratheesh Kannoth <rkannoth@...vell.com>
The subject line is:
[net PATCH] octeontx2: Fix klockwork and coverity issues
So you want these fixes backported to net? If so, you need to provide
Fixes: tags.
This patch is way too big. A fix patch generally fixes one thing, and
it documents what it fixes. Or it could be one class of problems, like
uninitialised variables etc. Its good to include the message from the
static analyser in the commit message.
Andrew
---
pw-bot: cr
Powered by blists - more mailing lists