From: Martin Varghese <martinvarghesenokia@gmail.com>
To: Ben Pfaff <blp@ovn.org>
Cc: dev@openvswitch.org, netdev@vger.kernel.org, pshelar@ovn.org,
Martin Varghese <martin.varghese@nokia.com>
Subject: Re: [ovs-dev] [PATCH] Change in openvswitch kernel module to support MPLS label depth of 3 in ingress direction.
Date: Mon, 21 Oct 2019 09:38:29 +0530 [thread overview]
Message-ID: <20191021040829.GA19653@martin-VirtualBox> (raw)
In-Reply-To: <20191020190706.GC25323@ovn.org>
On Sun, Oct 20, 2019 at 12:07:06PM -0700, Ben Pfaff wrote:
> On Sun, Oct 20, 2019 at 07:55:32PM +0530, Martin Varghese wrote:
> > From: Martin Varghese <martin.varghese@nokia.com>
> >
> > The openvswitch kernel module was supporting a MPLS label depth of 1
> > in the ingress direction though the userspace OVS supports a max depth
> > of 3 labels. This change enables openvswitch module to support a max
> > depth of 3 labels in the ingress.
> >
> > Signed-off-by: Martin Varghese <martin.varghese@nokia.com>
>
> Thanks for the patch!
>
> Usually, for kernel module changes, the workflow is to submit the change
> upstream to the Linux kernel first ("upstream first"). Then, afterward,
> we backport the upstream changes into the OVS repository.
>
> I see that you have CCed this to the Linux kernel networking list
> (netdev) but the patch itself is against the OVS repo. Probably, if you
> want to get reviews from netdev, you should instead post a patch against
> the net-next repository.
>
> Thanks again for working to improve Open vSwitch.
Thankyou for your mail.
The same changes are being discussed in netdev@vger.kernel.org.
Along with this patch, V2 of kernel patch for net-next repo is also submitted.
prev parent reply other threads:[~2019-10-21 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 14:25 [PATCH] Change in openvswitch kernel module to support MPLS label depth of 3 in ingress direction Martin Varghese
2019-10-20 19:07 ` [ovs-dev] " Ben Pfaff
2019-10-21 4:08 ` Martin Varghese [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=20191021040829.GA19653@martin-VirtualBox \
--to=martinvarghesenokia@gmail.com \
--cc=blp@ovn.org \
--cc=dev@openvswitch.org \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--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 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.