netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Kubecek <mkubecek@suse.cz>
To: Hannes Frederic Sowa <hannes@stressinduktion.org>,
	Jiri Benc <jbenc@redhat.com>,
	netdev@vger.kernel.org,
	Hideaki YOSHIFUJI <yoshfuji@linux-ipv6.org>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH v2 net-next] ipv6: router reachability probing
Date: Fri, 13 Dec 2013 13:51:16 +0100	[thread overview]
Message-ID: <20131213125116.GA28103@unicorn.suse.cz> (raw)
In-Reply-To: <20131212190810.GI4675@order.stressinduktion.org>

On Thu, Dec 12, 2013 at 08:08:10PM +0100, Hannes Frederic Sowa wrote:
> On Thu, Dec 12, 2013 at 10:10:05AM +0100, Michal Kubecek wrote:
> > 
> > On the other hand, the fix could be worth backporting to 3.4 stable
> > (more general, pre-3.6 stable branches) as the problem is much more
> > severe there.
> 
> Could you give it a try? I am not so sure if it really helps, maybe only in
> cases where more than one router is available.

I'll send a backport next week so that there is enough time for a review
before the original patch gets into mainline.

                                                          Michal Kubecek

      reply	other threads:[~2013-12-13 12:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-11 12:48 [PATCH v2 net-next] ipv6: router reachability probing Jiri Benc
2013-12-11 19:10 ` Hannes Frederic Sowa
2013-12-11 21:03   ` David Miller
2013-12-11 23:12 ` Michal Kubecek
2013-12-12  0:56   ` David Miller
2013-12-12  1:26     ` Hannes Frederic Sowa
2013-12-12  1:21   ` Hannes Frederic Sowa
2013-12-12  9:10     ` Michal Kubecek
2013-12-12 19:08       ` Hannes Frederic Sowa
2013-12-13 12:51         ` Michal Kubecek [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=20131213125116.GA28103@unicorn.suse.cz \
    --to=mkubecek@suse.cz \
    --cc=davem@davemloft.net \
    --cc=hannes@stressinduktion.org \
    --cc=jbenc@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=yoshfuji@linux-ipv6.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 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).