All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Mike Manning <mmanning@Brocade.com>
Cc: stable@vger.kernel.org, hannes@stressinduktion.org
Subject: Re: [PATCH 3.10] ipv6: move DAD and addrconf_verify processing to workqueue
Date: Fri, 16 Dec 2016 16:19:47 +0100	[thread overview]
Message-ID: <20161216151947.GG12172@1wt.eu> (raw)
In-Reply-To: <1caa5842-20d4-3f29-50db-8b0d78b4206b@brocade.com>

On Fri, Dec 16, 2016 at 02:43:49PM +0000, Mike Manning wrote:
> Hi Willy,
> I have submitted a patch for 751eb6b6042a. Please note that 43a43b604016 was already previously backported in 2e6f312e108b9f5609d601c4988c479e5cc9330d.
> 
> So the full set of patches should be in this order:
> 
> 2c861cc65ef4 ("ipv6: don't call fib6_run_gc() until routing is ready")
> b7b1bfce0bb6 ("ipv6: split duplicate address detection and router solicitation timer")
> c15b1ccadb32 ("ipv6: move DAD and addrconf_verify processing to workqueue")
> a9ed4a2986e1 ("ipv6: fix rtnl locking in setsockopt for anycast and multicast")
> 751eb6b6042a ("ipv6: addrconf: fix dev refcont leak when DAD failed")

Thank you Mike, I've queued them all now.

Willy

      reply	other threads:[~2016-12-16 15:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-16 10:16 [PATCH 3.10] ipv6: move DAD and addrconf_verify processing to workqueue Mike Manning
2016-12-16 10:40 ` Willy Tarreau
2016-12-16 10:51   ` Mike Manning
2016-12-16 10:58     ` Willy Tarreau
2016-12-16 11:30     ` Mike Manning
2016-12-16 11:36       ` Willy Tarreau
2016-12-16 14:43         ` Mike Manning
2016-12-16 15:19           ` Willy Tarreau [this message]

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=20161216151947.GG12172@1wt.eu \
    --to=w@1wt.eu \
    --cc=hannes@stressinduktion.org \
    --cc=mmanning@Brocade.com \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.