From: Jiri Benc <jbenc@redhat.com>
To: William Tu <u9012063@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>,
Pravin B Shelar <pshelar@ovn.org>
Subject: Re: [PATCHv2 net-next 2/2] openvswitch: add erspan version II support
Date: Fri, 12 Jan 2018 09:27:58 +0100 [thread overview]
Message-ID: <20180112092758.2f42b460@redhat.com> (raw)
In-Reply-To: <CALDO+SZ5v5Squu8zycVaWLL+zX2Hda1Q6ivs0mLqthCz4oZnyw@mail.gmail.com>
On Thu, 11 Jan 2018 08:34:14 -0800, William Tu wrote:
> I'd also prefer reverting ceaa001a170e since it's more clean but I
> also hope to have this feature in 4.15.
> How long does reverting take? Am I only able to submit the new patch
> after the reverting is merged? Or I can submit revert and this new
> patch in one series? I have little experience in reverting, can you
> suggest which way is better?
Send the revert for net (subject will be "[PATCH net] revert:
openvswitch: Add erspan tunnel support."). Don't forget to explain why
you're proposing a revert.
After it is accepted and applied to net.git, wait until the patch
appears in net-next.git. It may take a little while. After that, send
the new patch(es) for net-next.
Jiri
next prev parent reply other threads:[~2018-01-12 8:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-10 1:51 [PATCHv2 net-next 0/2] net: erspan: add support for openvswitch William Tu
2018-01-10 1:51 ` [PATCHv2 net-next 1/2] net: erspan: use bitfield instead of mask and offset William Tu
2018-01-10 1:51 ` [PATCHv2 net-next 2/2] openvswitch: add erspan version II support William Tu
2018-01-10 21:29 ` Jiri Benc
2018-01-10 21:35 ` Jiri Benc
2018-01-10 22:02 ` Jiri Benc
2018-01-11 16:34 ` William Tu
2018-01-12 8:27 ` Jiri Benc [this message]
2018-01-12 18:39 ` Pravin Shelar
2018-01-12 19:22 ` William Tu
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=20180112092758.2f42b460@redhat.com \
--to=jbenc@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pshelar@ovn.org \
--cc=u9012063@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 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).