From: patchwork-bot+netdevbpf@kernel.org
To: Dmitry Safonov <dima@arista.com>
Cc: linux-kernel@vger.kernel.org, dsahern@kernel.org,
edumazet@google.com, peterz@infradead.org, ardb@kernel.org,
gilligan@arista.com, davem@davemloft.net, 0x7f454c46@gmail.com,
fruggeri@arista.com, yoshfuji@linux-ipv6.org, kuba@kernel.org,
jbaron@akamai.com, jpoimboe@kernel.org, pabeni@redhat.com,
noureddine@arista.com, rostedt@goodmis.org,
netdev@vger.kernel.org
Subject: Re: [PATCH v6 0/5] net/tcp: Dynamically disable TCP-MD5 static key
Date: Fri, 02 Dec 2022 04:10:17 +0000 [thread overview]
Message-ID: <166995421700.16716.17446147162780881407.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221123173859.473629-1-dima@arista.com>
Hello:
This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 23 Nov 2022 17:38:54 +0000 you wrote:
> Changes from v5:
> - Corrected comment for static_key_fast_inc_not_negative() (Peter)
> - Renamed static_key_fast_inc_not_negative() =>
> static_key_fast_inc_not_disabled() (as suggested by Peter)
> - static_key_fast_inc_not_disabled() is exported and declared in the
> patch 1 that defines it, rather than in patch 3 that uses it (Peter)
>
> [...]
Here is the summary with links:
- [v6,1/5] jump_label: Prevent key->enabled int overflow
https://git.kernel.org/netdev/net-next/c/eb8c507296f6
- [v6,2/5] net/tcp: Separate tcp_md5sig_info allocation into tcp_md5sig_info_add()
https://git.kernel.org/netdev/net-next/c/f62c7517ffa1
- [v6,3/5] net/tcp: Disable TCP-MD5 static key on tcp_md5sig_info destruction
https://git.kernel.org/netdev/net-next/c/459837b522f7
- [v6,4/5] net/tcp: Do cleanup on tcp_md5_key_copy() failure
https://git.kernel.org/netdev/net-next/c/b389d1affc2c
- [v6,5/5] net/tcp: Separate initialization of twsk
https://git.kernel.org/netdev/net-next/c/c5b8b515a211
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-12-02 4:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-23 17:38 [PATCH v6 0/5] net/tcp: Dynamically disable TCP-MD5 static key Dmitry Safonov
2022-11-23 17:38 ` [PATCH v6 1/5] jump_label: Prevent key->enabled int overflow Dmitry Safonov
2022-11-25 7:59 ` Peter Zijlstra
2022-11-25 14:28 ` Dmitry Safonov
2022-12-01 22:31 ` Jakub Kicinski
2022-12-01 23:17 ` Dmitry Safonov
2022-12-01 23:36 ` Jakub Kicinski
2022-12-02 0:37 ` Dmitry Safonov
2022-11-23 17:38 ` [PATCH v6 2/5] net/tcp: Separate tcp_md5sig_info allocation into tcp_md5sig_info_add() Dmitry Safonov
2022-11-23 17:38 ` [PATCH v6 3/5] net/tcp: Disable TCP-MD5 static key on tcp_md5sig_info destruction Dmitry Safonov
2022-12-01 19:38 ` Eric Dumazet
2022-12-02 5:05 ` Eric Dumazet
2022-12-02 5:34 ` Eric Dumazet
2022-11-23 17:38 ` [PATCH v6 4/5] net/tcp: Do cleanup on tcp_md5_key_copy() failure Dmitry Safonov
2022-12-01 19:42 ` Eric Dumazet
2022-11-23 17:38 ` [PATCH v6 5/5] net/tcp: Separate initialization of twsk Dmitry Safonov
2022-12-01 19:44 ` Eric Dumazet
2022-12-02 4:10 ` 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=166995421700.16716.17446147162780881407.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=dima@arista.com \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=fruggeri@arista.com \
--cc=gilligan@arista.com \
--cc=jbaron@akamai.com \
--cc=jpoimboe@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=noureddine@arista.com \
--cc=pabeni@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=yoshfuji@linux-ipv6.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).