From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <edumazet@google.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
soheil@google.com, ncardwell@google.com, ycheng@google.com,
netdev@vger.kernel.org, eric.dumazet@gmail.com
Subject: Re: [PATCH net-next 0/3] tcp: add tcp_delack_max()
Date: Sun, 01 Oct 2023 12:20:29 +0000 [thread overview]
Message-ID: <169616282972.12522.9918976877085029703.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230920172943.4135513-1-edumazet@google.com>
Hello:
This series was applied to netdev/net-next.git (main)
by David S. Miller <davem@davemloft.net>:
On Wed, 20 Sep 2023 17:29:40 +0000 you wrote:
> First patches are adding const qualifiers to four existing helpers.
>
> Third patch adds a much needed companion feature to RTAX_RTO_MIN.
>
> Eric Dumazet (3):
> net: constify sk_dst_get() and __sk_dst_get() argument
> tcp: constify tcp_rto_min() and tcp_rto_min_us() argument
> tcp: derive delack_max from rto_min
>
> [...]
Here is the summary with links:
- [net-next,1/3] net: constify sk_dst_get() and __sk_dst_get() argument
https://git.kernel.org/netdev/net-next/c/5033f58d5fee
- [net-next,2/3] tcp: constify tcp_rto_min() and tcp_rto_min_us() argument
https://git.kernel.org/netdev/net-next/c/f68a181fcd3b
- [net-next,3/3] tcp: derive delack_max from rto_min
https://git.kernel.org/netdev/net-next/c/bbf80d713fe7
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-10-01 12:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 17:29 [PATCH net-next 0/3] tcp: add tcp_delack_max() Eric Dumazet
2023-09-20 17:29 ` [PATCH net-next 1/3] net: constify sk_dst_get() and __sk_dst_get() argument Eric Dumazet
2023-09-20 17:29 ` [PATCH net-next 2/3] tcp: constify tcp_rto_min() and tcp_rto_min_us() argument Eric Dumazet
2023-09-20 17:29 ` [PATCH net-next 3/3] tcp: derive delack_max from rto_min Eric Dumazet
2023-09-20 17:34 ` Soheil Hassas Yeganeh
2023-09-20 19:06 ` Neal Cardwell
2023-09-20 21:57 ` David Ahern
2023-09-21 2:16 ` Eric Dumazet
2023-09-21 12:37 ` David Ahern
2023-09-21 12:58 ` Eric Dumazet
2023-09-22 9:59 ` David Laight
2023-09-22 10:53 ` Eric Dumazet
2023-09-22 16:51 ` David Laight
2023-10-01 12: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=169616282972.12522.9918976877085029703.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=kuba@kernel.org \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=soheil@google.com \
--cc=ycheng@google.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.