From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com,
dsahern@kernel.org, kuniyu@amazon.com
Subject: Re: [PATCH net 0/6] tcp_metrics: series of fixes
Date: Thu, 03 Aug 2023 18:10:28 +0000 [thread overview]
Message-ID: <169108622801.23543.2612432757380166324.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230802131500.1478140-1-edumazet@google.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 2 Aug 2023 13:14:54 +0000 you wrote:
> This series contains a fix for addr_same() and various
> data-race annotations.
>
> We still have to address races over tm->tcpm_saddr and
> tm->tcpm_daddr later.
>
> Eric Dumazet (6):
> tcp_metrics: fix addr_same() helper
> tcp_metrics: annotate data-races around tm->tcpm_stamp
> tcp_metrics: annotate data-races around tm->tcpm_lock
> tcp_metrics: annotate data-races around tm->tcpm_vals[]
> tcp_metrics: annotate data-races around tm->tcpm_net
> tcp_metrics: fix data-race in tcpm_suck_dst() vs fastopen
>
> [...]
Here is the summary with links:
- [net,1/6] tcp_metrics: fix addr_same() helper
https://git.kernel.org/netdev/net/c/e6638094d7af
- [net,2/6] tcp_metrics: annotate data-races around tm->tcpm_stamp
https://git.kernel.org/netdev/net/c/949ad62a5d53
- [net,3/6] tcp_metrics: annotate data-races around tm->tcpm_lock
https://git.kernel.org/netdev/net/c/285ce119a3c6
- [net,4/6] tcp_metrics: annotate data-races around tm->tcpm_vals[]
https://git.kernel.org/netdev/net/c/8c4d04f6b443
- [net,5/6] tcp_metrics: annotate data-races around tm->tcpm_net
https://git.kernel.org/netdev/net/c/d5d986ce42c7
- [net,6/6] tcp_metrics: fix data-race in tcpm_suck_dst() vs fastopen
https://git.kernel.org/netdev/net/c/ddf251fa2bc1
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-08-03 18:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 13:14 [PATCH net 0/6] tcp_metrics: series of fixes Eric Dumazet
2023-08-02 13:14 ` [PATCH net 1/6] tcp_metrics: fix addr_same() helper Eric Dumazet
2023-08-02 15:04 ` David Ahern
2023-08-02 17:26 ` Kuniyuki Iwashima
2023-08-02 13:14 ` [PATCH net 2/6] tcp_metrics: annotate data-races around tm->tcpm_stamp Eric Dumazet
2023-08-02 15:06 ` David Ahern
2023-08-02 17:30 ` Kuniyuki Iwashima
2023-08-02 13:14 ` [PATCH net 3/6] tcp_metrics: annotate data-races around tm->tcpm_lock Eric Dumazet
2023-08-02 15:07 ` David Ahern
2023-08-02 17:35 ` Kuniyuki Iwashima
2023-08-02 13:14 ` [PATCH net 4/6] tcp_metrics: annotate data-races around tm->tcpm_vals[] Eric Dumazet
2023-08-02 15:09 ` David Ahern
2023-08-02 17:37 ` Kuniyuki Iwashima
2023-08-02 13:14 ` [PATCH net 5/6] tcp_metrics: annotate data-races around tm->tcpm_net Eric Dumazet
2023-08-02 15:12 ` David Ahern
2023-08-02 17:42 ` Kuniyuki Iwashima
2023-08-02 13:15 ` [PATCH net 6/6] tcp_metrics: fix data-race in tcpm_suck_dst() vs fastopen Eric Dumazet
2023-08-02 17:47 ` Kuniyuki Iwashima
2023-08-03 18: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=169108622801.23543.2612432757380166324.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).