From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Tobin C. Harding" Subject: Re: [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases Date: Tue, 15 May 2018 15:21:04 +1000 Message-ID: <20180515052104.GA10152@eros> References: <20180515025112.16647-1-dsahern@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org, Thomas.Winter@alliedtelesis.co.nz, idosch@mellanox.com, sharpd@cumulusnetworks.com, roopa@cumulusnetworks.com To: David Ahern Return-path: Received: from out2-smtp.messagingengine.com ([66.111.4.26]:59249 "EHLO out2-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752292AbeEOFVJ (ORCPT ); Tue, 15 May 2018 01:21:09 -0400 Content-Disposition: inline In-Reply-To: <20180515025112.16647-1-dsahern@gmail.com> Sender: netdev-owner@vger.kernel.org List-ID: Hi David, On Mon, May 14, 2018 at 07:51:05PM -0700, David Ahern wrote: > This patch set fixes a few append and replace uses cases for IPv6 and > adds test cases that codifies the expectations of how append and replace > are expected to work. Nood question: what commit does this apply on top of please. I attempted to apply the set on top of net-next commit (961423f9fcbc Merge branch 'sctp-Introduce-sctp_flush_ctx') patch 4 and 5 have merge conflicts (I stopped at 5). thanks, Tobin.