From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Benc Subject: Re: [PATCHv2 net-next 2/2] openvswitch: add erspan version II support Date: Fri, 12 Jan 2018 09:27:58 +0100 Message-ID: <20180112092758.2f42b460@redhat.com> References: <1515549082-4141-1-git-send-email-u9012063@gmail.com> <1515549082-4141-3-git-send-email-u9012063@gmail.com> <20180110223514.1e5030cd@redhat.com> <20180110230216.7e5a738d@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Linux Kernel Network Developers , Pravin B Shelar To: William Tu Return-path: Received: from mx1.redhat.com ([209.132.183.28]:60220 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754384AbeALI2C (ORCPT ); Fri, 12 Jan 2018 03:28:02 -0500 In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: 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