netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Ahern <dsahern@gmail.com>
To: David Miller <davem@davemloft.net>, dsahern@kernel.org
Cc: netdev@vger.kernel.org, Thomas.Winter@alliedtelesis.co.nz,
	idosch@mellanox.com, sharpd@cumulusnetworks.com,
	roopa@cumulusnetworks.com
Subject: Re: [PATCH net-next 0/7] net/ipv6: Fix route append and replace use cases
Date: Tue, 22 May 2018 14:44:32 -0600	[thread overview]
Message-ID: <6d61c529-5b51-dc3b-86ee-e912f1a8e0a8@gmail.com> (raw)
In-Reply-To: <20180522.144617.1003575784676243779.davem@davemloft.net>

On 5/22/18 12:46 PM, David Miller wrote:
> 
> Ok, I'll apply this series.
> 
> But if this breaks things for anyone in a practical way, I am unfortunately
> going to have to revert no matter how silly the current behavior may be.
> 

Understood. I have to try the best option first. I'll look at
regressions if they happen.

  reply	other threads:[~2018-05-22 20:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 17:26 [PATCH net-next 0/7] net/ipv6: Fix route append and replace use cases dsahern
2018-05-21 17:26 ` [PATCH net-next 1/7] mlxsw: spectrum_router: Add support for route append dsahern
2018-05-21 17:26 ` [PATCH net-next 2/7] net/ipv6: Simplify route replace and appending into multipath route dsahern
2018-05-21 17:26 ` [PATCH net-next 3/7] selftests: fib_tests: Add success-fail counts dsahern
2018-05-21 17:26 ` [PATCH net-next 4/7] selftests: fib_tests: Add command line options dsahern
2018-05-21 17:26 ` [PATCH net-next 5/7] selftests: fib_tests: Add option to pause after each test dsahern
2018-05-21 17:26 ` [PATCH net-next 6/7] selftests: fib_tests: Add ipv6 route add append replace tests dsahern
2018-05-21 17:26 ` [PATCH net-next 7/7] selftests: fib_tests: Add ipv4 " dsahern
2018-05-22 18:46 ` [PATCH net-next 0/7] net/ipv6: Fix route append and replace use cases David Miller
2018-05-22 20:44   ` David Ahern [this message]
2018-05-29 21:16     ` Thomas Winter
2018-07-02 21:23     ` David Ahern

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=6d61c529-5b51-dc3b-86ee-e912f1a8e0a8@gmail.com \
    --to=dsahern@gmail.com \
    --cc=Thomas.Winter@alliedtelesis.co.nz \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=idosch@mellanox.com \
    --cc=netdev@vger.kernel.org \
    --cc=roopa@cumulusnetworks.com \
    --cc=sharpd@cumulusnetworks.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).