From: Jakub Kicinski <kuba@kernel.org>
To: Ilya Maximets <i.maximets@ovn.org>
Cc: Roi Dayan <roid@nvidia.com>,
Johannes Berg <johannes@sipsolutions.net>,
dev@openvswitch.org, Toms Atteka <cpp.code.lv@gmail.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
davem@davemloft.net, David Ahern <dsahern@gmail.com>,
Jiri Pirko <jiri@resnulli.us>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [ovs-dev] [PATCH net-next v8] net: openvswitch: IPv6: Add IPv6 extension header support
Date: Tue, 8 Mar 2022 12:17:06 -0800 [thread overview]
Message-ID: <20220308121706.5e406e67@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <1eca594f-ec8c-b54a-92f3-e561fa049015@ovn.org>
On Tue, 8 Mar 2022 19:25:31 +0100 Ilya Maximets wrote:
> > since its rc7 we end up with kernel and ovs broken with each other.
> > can we revert the kernel patches anyway and introduce them again later
> > when ovs userspace is also updated?
>
> I don't think this patch is part of 5-17-rc7. AFAICT, it's a candidate
> for 5.18, so we should still have a bit of time. Am I missing something?
You are correct, it's going to hit Linus's tree during the 5.18 merge
window. It seems we're close enough to a resolution to focus on a fix
instead.
next prev parent reply other threads:[~2022-03-08 20:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 0:54 [PATCH net-next v8] net: openvswitch: IPv6: Add IPv6 extension header support Toms Atteka
2022-02-25 10:40 ` patchwork-bot+netdevbpf
2022-03-02 10:03 ` [ovs-dev] " Roi Dayan
2022-03-02 10:50 ` Roi Dayan
2022-03-02 13:59 ` Eelco Chaudron
2022-03-07 8:49 ` Roi Dayan
2022-03-07 20:26 ` Jakub Kicinski
2022-03-07 22:14 ` Ilya Maximets
2022-03-07 22:46 ` Jakub Kicinski
2022-03-08 0:04 ` Ilya Maximets
2022-03-08 5:45 ` Jakub Kicinski
2022-03-08 8:21 ` Johannes Berg
2022-03-08 14:12 ` Ilya Maximets
2022-03-08 14:39 ` Roi Dayan
2022-03-08 18:25 ` Ilya Maximets
2022-03-08 20:17 ` Jakub Kicinski [this message]
2022-03-08 16:17 ` Jakub Kicinski
2022-03-08 19:33 ` Ilya Maximets
2022-03-08 20:16 ` Jakub Kicinski
2022-03-09 7:49 ` Roi Dayan
2022-03-09 13:43 ` Ilya Maximets
2022-03-09 16:17 ` Jakub Kicinski
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=20220308121706.5e406e67@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=cpp.code.lv@gmail.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=dsahern@gmail.com \
--cc=i.maximets@ovn.org \
--cc=jiri@resnulli.us \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pablo@netfilter.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 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.