From: patchwork-bot+netdevbpf@kernel•org
To: Leon Romanovsky <leon@kernel•org>
Cc: dsahern@kernel•org, davem@davemloft•net, edumazet@google•com,
kuba@kernel•org, pabeni@redhat•com, skagan@nvidia•com,
netdev@vger•kernel.org, bagasdotme@gmail•com,
regressions@leemhuis•info
Subject: Re: [PATCH net-next] tcp: Revert no longer abort SYN_SENT when receiving some ICMP
Date: Tue, 09 Jan 2024 03:20:24 +0000 [thread overview]
Message-ID: <170477042468.7389.10437753587986940246.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <14459261ea9f9c7d7dfb28eb004ce8734fa83ade.1704185904.git.leonro@nvidia.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Tue, 2 Jan 2024 11:00:57 +0200 you wrote:
> From: Shachar Kagan <skagan@nvidia•com>
>
> This reverts commit 0a8de364ff7a14558e9676f424283148110384d6.
>
> Shachar reported that Vagrant (https://www.vagrantup.com/), which is
> very popular tool to manage fleet of VMs stopped to work after commit
> citied in Fixes line.
>
> [...]
Here is the summary with links:
- [net-next] tcp: Revert no longer abort SYN_SENT when receiving some ICMP
https://git.kernel.org/netdev/net-next/c/b59db45d7eba
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:[~2024-01-09 3:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 9:00 [PATCH net-next] tcp: Revert no longer abort SYN_SENT when receiving some ICMP Leon Romanovsky
2024-01-02 9:46 ` Eric Dumazet
2024-01-02 9:58 ` Leon Romanovsky
2024-01-02 10:03 ` Eric Dumazet
2024-01-02 10:11 ` Eric Dumazet
2024-01-02 11:41 ` Leon Romanovsky
2024-01-02 15:31 ` Eric Dumazet
2024-01-02 18:01 ` Leon Romanovsky
2024-01-02 18:33 ` Eric Dumazet
2024-01-02 19:13 ` Leon Romanovsky
2024-01-02 22:02 ` Jakub Kicinski
2024-01-03 6:00 ` Leon Romanovsky
2024-01-08 15:52 ` Eric Dumazet
2024-01-09 13:26 ` Leon Romanovsky
2024-01-09 3: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=170477042468.7389.10437753587986940246.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=bagasdotme@gmail$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=dsahern@kernel$(echo .)org \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=leon@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
--cc=regressions@leemhuis$(echo .)info \
--cc=skagan@nvidia$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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