From: patchwork-bot+netdevbpf@kernel.org
To: Ilya Maximets <i.maximets@ovn.org>
Cc: kuba@kernel.org, roid@nvidia.com, davem@davemloft.net,
pshelar@ovn.org, cpp.code.lv@gmail.com, netdev@vger.kernel.org,
dev@openvswitch.org, linux-kernel@vger.kernel.org,
johannes@sipsolutions.net, aconole@redhat.com
Subject: Re: [PATCH net-next v2] net: openvswitch: fix uAPI incompatibility with existing user space
Date: Fri, 11 Mar 2022 04:30:13 +0000 [thread overview]
Message-ID: <164697301313.12732.14395145202660656158.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220309222033.3018976-1-i.maximets@ovn.org>
Hello:
This patch was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 9 Mar 2022 23:20:33 +0100 you wrote:
> Few years ago OVS user space made a strange choice in the commit [1]
> to define types only valid for the user space inside the copy of a
> kernel uAPI header. '#ifndef __KERNEL__' and another attribute was
> added later.
>
> This leads to the inevitable clash between user space and kernel types
> when the kernel uAPI is extended. The issue was unveiled with the
> addition of a new type for IPv6 extension header in kernel uAPI.
>
> [...]
Here is the summary with links:
- [net-next,v2] net: openvswitch: fix uAPI incompatibility with existing user space
https://git.kernel.org/netdev/net-next/c/1926407a4ab0
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-03-11 4:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-09 22:20 [PATCH net-next v2] net: openvswitch: fix uAPI incompatibility with existing user space Ilya Maximets
2022-03-10 8:24 ` Nicolas Dichtel
2022-03-10 18:44 ` Aaron Conole
2022-03-14 18:33 ` Roi Dayan
2022-03-14 19:40 ` Ilya Maximets
2022-04-07 8:02 ` Vlad Buslov
2022-04-07 10:22 ` Ilya Maximets
2022-05-12 10:19 ` Eelco Chaudron
2022-05-12 10:08 ` Vlad Buslov
2022-05-17 11:10 ` Eelco Chaudron
2022-05-23 12:54 ` Eelco Chaudron
2022-05-31 14:39 ` Eelco Chaudron
2022-03-11 4:30 ` 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=164697301313.12732.14395145202660656158.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aconole@redhat.com \
--cc=cpp.code.lv@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=i.maximets@ovn.org \
--cc=johannes@sipsolutions.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=roid@nvidia.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;
as well as URLs for NNTP newsgroup(s).