From: patchwork-bot+netdevbpf@kernel.org
To: Tim Gardner <tim.gardner@canonical.com>
Cc: pkushwaha@marvell.com, aelior@marvell.com,
GR-everest-linux-l2@marvell.com, davem@davemloft.net,
kuba@kernel.org, smalin@marvell.com, okulkarni@marvell.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2][next] qed: Initialize debug string array
Date: Fri, 08 Oct 2021 14:20:07 +0000 [thread overview]
Message-ID: <163370280707.5508.8344854515850968604.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211007120413.8642-1-tim.gardner@canonical.com>
Hello:
This patch was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 7 Oct 2021 06:04:13 -0600 you wrote:
> Coverity complains of an uninitialized variable.
>
> CID 120847 (#1 of 1): Uninitialized scalar variable (UNINIT)
> 3. uninit_use_in_call: Using uninitialized value *sw_platform_str when calling qed_dump_str_param. [show details]
> 1344 offset += qed_dump_str_param(dump_buf + offset,
> 1345 dump, "sw-platform", sw_platform_str);
>
> [...]
Here is the summary with links:
- [v2,next] qed: Initialize debug string array
https://git.kernel.org/netdev/net-next/c/d5ac07dfbd2b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-10-08 14:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 14:02 [PATCH][next][RFC] qed: Initialize debug string array Tim Gardner
2021-10-07 5:11 ` [EXT] " Prabhakar Kushwaha
2021-10-07 12:04 ` [PATCH v2][next] " Tim Gardner
2021-10-08 14:20 ` patchwork-bot+netdevbpf [this message]
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=163370280707.5508.8344854515850968604.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=GR-everest-linux-l2@marvell.com \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=okulkarni@marvell.com \
--cc=pkushwaha@marvell.com \
--cc=smalin@marvell.com \
--cc=tim.gardner@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.