From: patchwork-bot+netdevbpf@kernel.org
To: Chuck Lever <cel@kernel.org>
Cc: netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
chuck.lever@oracle.com
Subject: Re: [PATCH v2 0/2] Fix implicit sign conversions in handshake upcall
Date: Mon, 02 Oct 2023 19:40:29 +0000 [thread overview]
Message-ID: <169627562979.13580.16928932673781658567.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <169530154802.8905.2645661840284268222.stgit@oracle-102.nfsv4bat.org>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 21 Sep 2023 09:07:14 -0400 you wrote:
> An internal static analysis tool noticed some implicit sign
> conversions for some of the arguments in the handshake upcall
> protocol.
>
> ---
>
> Chuck Lever (2):
> handshake: Fix sign of socket file descriptor fields
> handshake: Fix sign of key_serial_t fields
>
> [...]
Here is the summary with links:
- [v2,1/2] handshake: Fix sign of socket file descriptor fields
https://git.kernel.org/netdev/net-next/c/a6b07a51b161
- [v2,2/2] handshake: Fix sign of key_serial_t fields
https://git.kernel.org/netdev/net-next/c/160f404495aa
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:[~2023-10-02 19:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-21 13:07 [PATCH v2 0/2] Fix implicit sign conversions in handshake upcall Chuck Lever
2023-09-21 13:07 ` [PATCH v2 1/2] handshake: Fix sign of socket file descriptor fields Chuck Lever
2023-09-21 13:08 ` [PATCH v2 2/2] handshake: Fix sign of key_serial_t fields Chuck Lever
2023-09-21 21:56 ` [PATCH v2 0/2] Fix implicit sign conversions in handshake upcall Simon Horman
2023-10-02 19: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=169627562979.13580.16928932673781658567.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=cel@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=netdev@vger.kernel.org \
/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).