From: David Ahern <dsahern@gmail.com>
To: "Tobin C. Harding" <tobin@apporbit.com>
Cc: netdev@vger.kernel.org, Thomas.Winter@alliedtelesis.co.nz,
idosch@mellanox.com, sharpd@cumulusnetworks.com,
roopa@cumulusnetworks.com
Subject: Re: [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases
Date: Mon, 14 May 2018 23:54:08 -0600 [thread overview]
Message-ID: <458fe36b-355a-f11e-32b4-8a139c26a298@gmail.com> (raw)
In-Reply-To: <20180515052104.GA10152@eros>
On 5/14/18 11:21 PM, Tobin C. Harding wrote:
> 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).
Base commit is:
commit 289e1f4e9e4a09c73a1c0152bb93855ea351ccda
Author: Anders Roxell <anders.roxell@linaro.org>
Date: Sun May 13 21:48:30 2018 +0200
net: ipv4: ipconfig: fix unused variable
I don't see 961423f9fcbc in any tree.
next prev parent reply other threads:[~2018-05-15 5:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-15 2:51 [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 1/7] mlxsw: spectrum_router: Add support for route append David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 2/7] net/ipv6: Simplify route replace and appending into multipath route David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 3/7] selftests: fib_tests: Add success-fail counts David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 4/7] selftests: fib_tests: Add command line options David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 5/7] selftests: fib_tests: Add option to pause after each test David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 6/7] selftests: fib_tests: Add ipv6 route add append replace tests David Ahern
2018-05-15 2:51 ` [PATCH RFC net-next 7/7] selftests: fib_tests: Add ipv4 " David Ahern
2018-05-15 5:21 ` [PATCH RFC net-next 0/7] net/ipv6: Fix route append and replace use cases Tobin C. Harding
2018-05-15 5:54 ` David Ahern [this message]
2018-05-15 6:12 ` Tobin C. Harding
2018-05-15 6:25 ` David Ahern
2018-05-15 6:38 ` Tobin C. Harding
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=458fe36b-355a-f11e-32b4-8a139c26a298@gmail.com \
--to=dsahern@gmail.com \
--cc=Thomas.Winter@alliedtelesis.co.nz \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sharpd@cumulusnetworks.com \
--cc=tobin@apporbit.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).