From: patchwork-bot+netdevbpf@kernel.org
To: Alexandra Winter <wintera@linux.ibm.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
linux-s390@vger.kernel.org, hca@linux.ibm.com
Subject: Re: [PATCH net 0/3] s390/net: Cleanup some code checker findings
Date: Wed, 11 May 2022 11:40:12 +0000 [thread overview]
Message-ID: <165226921258.16940.11518826783364912077.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220510070508.334726-1-wintera@linux.ibm.com>
Hello:
This series was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Tue, 10 May 2022 09:05:05 +0200 you wrote:
> clean up smatch findings in legacy code. I was not able to provoke
> any real failures on my systems, but other hardware reactions,
> timing conditions or compiler output, may cause failures.
>
> There are still 2 smatch warnings left in s390/net:
>
> drivers/s390/net/ctcm_main.c:1326 add_channel() warn: missing error code 'rc'
> This one is a false positive.
>
> [...]
Here is the summary with links:
- [net,1/3] s390/ctcm: fix variable dereferenced before check
https://git.kernel.org/netdev/net/c/2c50c6867c85
- [net,2/3] s390/ctcm: fix potential memory leak
https://git.kernel.org/netdev/net/c/0c0b20587b9f
- [net,3/3] s390/lcs: fix variable dereferenced before check
https://git.kernel.org/netdev/net/c/671bb35c8e74
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:[~2022-05-11 11:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 7:05 [PATCH net 0/3] s390/net: Cleanup some code checker findings Alexandra Winter
2022-05-10 7:05 ` [PATCH net 1/3] s390/ctcm: fix variable dereferenced before check Alexandra Winter
2022-05-10 7:05 ` [PATCH net 2/3] s390/ctcm: fix potential memory leak Alexandra Winter
2022-05-10 7:05 ` [PATCH net 3/3] s390/lcs: fix variable dereferenced before check Alexandra Winter
2022-05-11 11:40 ` 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=165226921258.16940.11518826783364912077.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=wintera@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).