From: patchwork-bot+netdevbpf@kernel.org
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: pshelar@ovn.org, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org, netdev@vger.kernel.org,
dev@openvswitch.org
Subject: Re: [PATCH v2 1/2] net: openvswitch: Use struct_size()
Date: Tue, 17 Oct 2023 13:50:24 +0000 [thread overview]
Message-ID: <169755062484.25061.3738739418791842854.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <e5122b4ff878cbf3ed72653a395ad5c4da04dc1e.1697264974.git.christophe.jaillet@wanadoo.fr>
Hello:
This series was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 14 Oct 2023 08:34:52 +0200 you wrote:
> Use struct_size() instead of hand writing it.
> This is less verbose and more robust.
>
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> v2: No change
>
> [...]
Here is the summary with links:
- [v2,1/2] net: openvswitch: Use struct_size()
https://git.kernel.org/netdev/net-next/c/df3bf90fef28
- [v2,2/2] net: openvswitch: Annotate struct mask_array with __counted_by
https://git.kernel.org/netdev/net-next/c/7713ec844756
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-17 13:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-14 6:34 [PATCH v2 1/2] net: openvswitch: Use struct_size() Christophe JAILLET
2023-10-14 6:34 ` [PATCH v2 2/2] net: openvswitch: Annotate struct mask_array with __counted_by Christophe JAILLET
2023-10-15 2:29 ` Kees Cook
2023-10-15 4:53 ` Julia Lawall
2023-10-15 7:20 ` Christophe JAILLET
2023-10-17 9:10 ` [ovs-dev] " Simon Horman
2023-10-17 9:09 ` [ovs-dev] [PATCH v2 1/2] net: openvswitch: Use struct_size() Simon Horman
2023-10-17 13:50 ` 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=169755062484.25061.3738739418791842854.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pshelar@ovn.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).