From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
horms@kernel.org, ncardwell@google.com, kuniyu@google.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/2] tcp: remove tcp_rate.c
Date: Fri, 23 Jan 2026 02:40:15 +0000 [thread overview]
Message-ID: <176913601584.2368645.14555144176625626997.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260121095923.3134639-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 21 Jan 2026 09:59:21 +0000 you wrote:
> Move tcp_rate_gen() to tcp_input.c and tcp_rate_check_app_limited()
> to tcp.c for better code generation.
>
> tcp_rate.c was interesting from code maintenance perspective
> but was adding cpu costs.
>
> Eric Dumazet (2):
> tcp: move tcp_rate_gen to tcp_input.c
> tcp: move tcp_rate_check_app_limited() to tcp.c
>
> [...]
Here is the summary with links:
- [net-next,1/2] tcp: move tcp_rate_gen to tcp_input.c
https://git.kernel.org/netdev/net-next/c/b814bdcecd79
- [net-next,2/2] tcp: move tcp_rate_check_app_limited() to tcp.c
https://git.kernel.org/netdev/net-next/c/bc1f0b1c98f5
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:[~2026-01-23 2:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 9:59 [PATCH net-next 0/2] tcp: remove tcp_rate.c Eric Dumazet
2026-01-21 9:59 ` [PATCH net-next 1/2] tcp: move tcp_rate_gen to tcp_input.c Eric Dumazet
2026-01-21 16:16 ` Neal Cardwell
2026-01-21 9:59 ` [PATCH net-next 2/2] tcp: move tcp_rate_check_app_limited() to tcp.c Eric Dumazet
2026-01-21 16:19 ` Neal Cardwell
2026-01-23 2:40 ` 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=176913601584.2368645.14555144176625626997.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.dumazet@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@google.com \
--cc=ncardwell@google.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