From: Martin Varghese <martinvarghesenokia@gmail.com>
To: Cong Wang <xiyou.wangcong@gmail.com>
Cc: David Miller <davem@davemloft.net>,
Linux Kernel Network Developers <netdev@vger.kernel.org>,
pravin shelar <pshelar@ovn.org>,
Jamal Hadi Salim <jhs@mojatatu.com>,
Jiri Pirko <jiri@resnulli.us>,
martin.varghese@nokia.com
Subject: Re: [PATCH v3 net-next] Enhanced skb_mpls_pop to update ethertype of the packet in all the cases when an ethernet header is present is the packet.
Date: Sun, 1 Dec 2019 10:27:27 +0530 [thread overview]
Message-ID: <20191201045727.GA2548@martin-VirtualBox> (raw)
In-Reply-To: <CAM_iQpWu9DQ06FYo7xtuLFnHP-wx35Uva_0-im7XwemKtLno0A@mail.gmail.com>
On Fri, Nov 29, 2019 at 10:07:53PM -0800, Cong Wang wrote:
> On Wed, Nov 27, 2019 at 11:24 AM David Miller <davem@davemloft.net> wrote:
> >
> >
> > net-next is closed, please resubmit this when net-next opens back up.
> >
>
> I think this patch is intended for -net as it fixes a bug in OVS?
>
> Martin, if it is the case, please resend with targeting to -net instead.
> Also, please make the $subject shorter.
>
There are few upcoming features to net-next from my side which relies on this fix.
In that case should i post against both net and net-next ?
Please advice
Thanks
Martin
next prev parent reply other threads:[~2019-12-01 4:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 10:01 [PATCH v3 net-next] Enhanced skb_mpls_pop to update ethertype of the packet in all the cases when an ethernet header is present is the packet Martin Varghese
2019-11-27 19:24 ` David Miller
2019-11-30 6:07 ` Cong Wang
2019-12-01 4:57 ` Martin Varghese [this message]
2019-12-01 5:50 ` Cong Wang
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=20191201045727.GA2548@martin-VirtualBox \
--to=martinvarghesenokia@gmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=martin.varghese@nokia.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=xiyou.wangcong@gmail.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.