From: patchwork-bot+netdevbpf@kernel.org
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: davem@davemloft.net, kuba@kernel.org, netdev@vger.kernel.org,
edumazet@google.com
Subject: Re: [PATCH net-next 0/2] net: annotate accesses to dev->gso_max_{size|segs}
Date: Mon, 22 Nov 2021 13:00:13 +0000 [thread overview]
Message-ID: <163758601373.20556.2061738034689274771.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211119154332.4110795-1-eric.dumazet@gmail.com>
Hello:
This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:
On Fri, 19 Nov 2021 07:43:30 -0800 you wrote:
> From: Eric Dumazet <edumazet@google.com>
>
> Generalize use of netif_set_gso_max_{size|segs} helpers and document
> lockless reads from sk_setup_caps()
>
> Eric Dumazet (2):
> net: annotate accesses to dev->gso_max_size
> net: annotate accesses to dev->gso_max_segs
>
> [...]
Here is the summary with links:
- [net-next,1/2] net: annotate accesses to dev->gso_max_size
https://git.kernel.org/netdev/net-next/c/4b66d2161b81
- [net-next,2/2] net: annotate accesses to dev->gso_max_segs
https://git.kernel.org/netdev/net-next/c/6d872df3e3b9
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:[~2021-11-22 13:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-19 15:43 [PATCH net-next 0/2] net: annotate accesses to dev->gso_max_{size|segs} Eric Dumazet
2021-11-19 15:43 ` [PATCH net-next 1/2] net: annotate accesses to dev->gso_max_size Eric Dumazet
2021-11-19 15:43 ` [PATCH net-next 2/2] net: annotate accesses to dev->gso_max_segs Eric Dumazet
2021-11-19 15:48 ` [PATCH net-next 0/2] net: annotate accesses to dev->gso_max_{size|segs} David Miller
2021-11-22 13: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=163758601373.20556.2061738034689274771.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=netdev@vger.kernel.org \
/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).