On Fri, Jul 8, 2022 at 10:09 PM Greg Rose <gvrose8...@gmail.com> wrote: > diff --git a/Documentation/internals/contributing/backporting-patches.rst > b/Documentation/internals/contributing/backporting-patches.rst > index 162e9d209..8370c954d 100644 > --- a/Documentation/internals/contributing/backporting-patches.rst > +++ b/Documentation/internals/contributing/backporting-patches.rst > @@ -119,6 +119,13 @@ userspace changes. > How to backport kernel patches > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > +These instructions only apply to Open vSwitch releases 2.16 and older. > +As of Open vSwitch branch 2.17 the Open vSwitch kernel module is no > +longer supported and only the Linux openvswitch kernel module is used. > +In the case of Open vSwitch releases 2.16 and older kernel backports > +may be required for bux fixes and feature implementation so these > +instructions are preserved for that reason. > + > First, the patch should be submitted upstream to `netdev`. When the patch has > been applied to `net-next`, it is ready to be backported. Starting from the > Linux tree, use ``git format-patch`` to format each patch that should be
Adding to Ilya comments. Here, should those versions here be bumped by one too? Leaving it as proposed in this patch, this saves us from potential backporting effort to 2.17 too :-). -- David Marchand _______________________________________________ dev mailing list d...@openvswitch.org https://mail.openvswitch.org/mailman/listinfo/ovs-dev
