From: patchwork-bot+netdevbpf@kernel.org
To: Jason Xing <kerneljasonxing@gmail.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, dsahern@kernel.org, netdev@vger.kernel.org,
kernelxing@tencent.com
Subject: Re: [PATCH net-next v3 0/2] tcp: add tcp_warn_once() common helper
Date: Wed, 30 Oct 2024 13:30:31 +0000 [thread overview]
Message-ID: <173029503127.1339926.3838953903282931840.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241023081452.9151-1-kerneljasonxing@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 23 Oct 2024 16:14:50 +0800 you wrote:
> From: Jason Xing <kernelxing@tencent.com>
>
> Paolo Abeni suggested we can introduce a new helper to cover more cases
> in the future for better debug.
>
> Jason Xing (2):
> tcp: add a common helper to debug the underlying issue
> tcp: add more warn of socket in tcp_send_loss_probe()
>
> [...]
Here is the summary with links:
- [net-next,v3,1/2] tcp: add a common helper to debug the underlying issue
https://git.kernel.org/netdev/net-next/c/386c2b877b97
- [net-next,v3,2/2] tcp: add more warn of socket in tcp_send_loss_probe()
https://git.kernel.org/netdev/net-next/c/668d663989c7
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-10-30 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-23 8:14 [PATCH net-next v3 0/2] tcp: add tcp_warn_once() common helper Jason Xing
2024-10-23 8:14 ` [PATCH net-next v3 1/2] tcp: add a common helper to debug the underlying issue Jason Xing
2024-10-23 8:14 ` [PATCH net-next v3 2/2] tcp: add more warn of socket in tcp_send_loss_probe() Jason Xing
2024-10-30 13: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=173029503127.1339926.3838953903282931840.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=kerneljasonxing@gmail.com \
--cc=kernelxing@tencent.com \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.