From: patchwork-bot+netdevbpf@kernel.org
To: Feng Gao <gfree.wind@outlook.com>
Cc: martin.lau@linux.dev, daniel@iogearbox.net,
john.fastabend@gmail.com, song@kernel.org, yhs@fb.com,
kpsingh@kernel.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, bpf@vger.kernel.org,
netdev@vger.kernel.org, gfree.wind@gmail.com
Subject: Re: [PATCH net] net: bpf: Use the protocol's set_rcvlowat behavior if there is one
Date: Mon, 08 Aug 2022 10:00:13 +0000 [thread overview]
Message-ID: <165995281320.20342.8222764157601079891.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <OSZP286MB140479B6DBDB0F13651A55F9959F9@OSZP286MB1404.JPNP286.PROD.OUTLOOK.COM>
Hello:
This patch was applied to netdev/net.git (master)
by David S. Miller <davem@davemloft.net>:
On Thu, 4 Aug 2022 23:04:21 +0800 you wrote:
> From: Gao Feng <gfree.wind@gmail.com>
>
> The commit d1361840f8c5 ("tcp: fix SO_RCVLOWAT and RCVBUF autotuning")
> add one new (struct proto_ops)->set_rcvlowat method so that a protocol
> can override the default setsockopt(SO_RCVLOWAT) behavior.
>
> The prior bpf codes don't check and invoke the protos's set_rcvlowat,
> now correct it.
>
> [...]
Here is the summary with links:
- [net] net: bpf: Use the protocol's set_rcvlowat behavior if there is one
https://git.kernel.org/netdev/net/c/f574f7f839fc
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:[~2022-08-08 10:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 15:04 [PATCH net] net: bpf: Use the protocol's set_rcvlowat behavior if there is one gfree.wind
2022-08-08 10:00 ` 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=165995281320.20342.8222764157601079891.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gfree.wind@gmail.com \
--cc=gfree.wind@outlook.com \
--cc=john.fastabend@gmail.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=song@kernel.org \
--cc=yhs@fb.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