From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Teco Boot <teco@inf-net.nl>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match
Date: Sat, 10 Aug 2013 14:15:30 +0200 [thread overview]
Message-ID: <20130810121530.GQ14001@order.stressinduktion.org> (raw)
In-Reply-To: <2A0809D4-EBF1-4646-9564-2B7F54956B41@inf-net.nl>
On Sat, Aug 10, 2013 at 01:39:12PM +0200, Teco Boot wrote:
> The hang problem in 3.8.0-28 has lower priority for me. Maybe I'll check current -net-next later. Don't hold your breath.
Ah, one more thing: Please don't test net-next but net
<https://git.kernel.org/cgit/linux/kernel/git/davem/net.git/>.
All relevant patches are in there. They will first show up in net-next when
David merges net back to net-next. That's because the other patches are also
queued up for 3.11 inclusion.
Greetings,
Hannes
next prev parent reply other threads:[~2013-08-10 12:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 0:34 [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match Hannes Frederic Sowa
2013-08-07 19:58 ` Teco Boot
2013-08-07 20:06 ` Hannes Frederic Sowa
2013-08-09 14:12 ` Teco Boot
2013-08-09 14:19 ` Hannes Frederic Sowa
2013-08-09 14:40 ` Teco Boot
2013-08-09 14:57 ` Hannes Frederic Sowa
2013-08-10 11:39 ` Teco Boot
2013-08-10 12:03 ` Hannes Frederic Sowa
2013-08-13 8:02 ` Teco Boot
2013-08-13 8:15 ` David Miller
2013-08-14 6:40 ` Teco Boot
2013-08-14 7:55 ` David Miller
2013-08-14 7:59 ` Teco Boot
2013-08-14 8:06 ` Teco Boot
2013-08-14 10:06 ` Hannes Frederic Sowa
2013-08-10 12:15 ` Hannes Frederic Sowa [this message]
2015-12-02 9:55 ` [PATCH net 1/1] via-rhine: fix VLAN receive handling regression Teco Boot
2015-12-03 20:11 ` David Miller
2013-08-08 0:17 ` [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match David Miller
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=20130810121530.GQ14001@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=teco@inf-net.nl \
/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