From: patchwork-bot+netdevbpf@kernel.org
To: Kuniyuki Iwashima <kuniyu@amazon.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, kuni1840@gmail.com,
netdev@vger.kernel.org
Subject: Re: [PATCH v1 net 0/2] tcp: Fix bind() regression for dual-stack wildcard address.
Date: Wed, 15 Mar 2023 07:30:18 +0000 [thread overview]
Message-ID: <167886541889.32297.4810741018223268568.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230312031904.4674-1-kuniyu@amazon.com>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Sat, 11 Mar 2023 19:19:02 -0800 you wrote:
> The first patch fixes the regression reported in [0], and the second
> patch adds a test for similar cases to catch future regression.
>
> [0]: https://lore.kernel.org/netdev/e21bf153-80b0-9ec0-15ba-e04a4ad42c34@redhat.com/
>
>
> Kuniyuki Iwashima (2):
> tcp: Fix bind() conflict check for dual-stack wildcard address.
> selftest: Add test for bind() conflicts.
>
> [...]
Here is the summary with links:
- [v1,net,1/2] tcp: Fix bind() conflict check for dual-stack wildcard address.
https://git.kernel.org/netdev/net/c/d9ba99342855
- [v1,net,2/2] selftest: Add test for bind() conflicts.
https://git.kernel.org/netdev/net/c/13715acf8ab5
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-03-15 7:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 3:19 [PATCH v1 net 0/2] tcp: Fix bind() regression for dual-stack wildcard address Kuniyuki Iwashima
2023-03-12 3:19 ` [PATCH v1 net 1/2] tcp: Fix bind() conflict check " Kuniyuki Iwashima
2023-03-12 11:42 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-15 7:26 ` Jakub Kicinski
2023-03-15 8:05 ` Thorsten Leemhuis
2023-03-15 19:52 ` Jakub Kicinski
2023-03-13 12:39 ` Eric Dumazet
2023-03-13 16:12 ` Paul Holzinger
2023-03-14 18:34 ` Martin KaFai Lau
2023-03-12 3:19 ` [PATCH v1 net 2/2] selftest: Add test for bind() conflicts Kuniyuki Iwashima
2023-03-15 7:30 ` 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=167886541889.32297.4810741018223268568.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=kuni1840@gmail.com \
--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).