[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CALDO+Sbsyfutop_fvSimOdx=pUf_iCG3PX2T_xtOD15vKQL5Rg@mail.gmail.com>
Date: Fri, 12 Jan 2018 11:22:21 -0800
From: William Tu <u9012063@...il.com>
To: Pravin Shelar <pshelar@....org>
Cc: Jiri Benc <jbenc@...hat.com>,
Linux Kernel Network Developers <netdev@...r.kernel.org>
Subject: Re: [PATCHv2 net-next 2/2] openvswitch: add erspan version II support
On Fri, Jan 12, 2018 at 10:39 AM, Pravin Shelar <pshelar@....org> wrote:
> On Fri, Jan 12, 2018 at 12:27 AM, Jiri Benc <jbenc@...hat.com> wrote:
>> 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.
>>
>
> I agree, Once we have the V2 interface, this current ERSAN interface
> unlikely to be used by any one, so it would be nice to get rid of the
> old interface while we can.
Thanks Jiri and Pravin.
I will send out revert patch request.
William
Powered by blists - more mailing lists