From: Ville Nuorvala <vnuorval@tcs.hut.fi>
To: "David S. Miller" <davem@davemloft.net>
Cc: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>,
Thomas Graf <tgraf@suug.ch>,
kim.nordlund@nokia.com, lksctp-developers@lists.sourceforge.net,
netdev@vger.kernel.org
Subject: [PATCH 0/13] [RFC] Fix problems with IPv6 routing subtrees and source address selection
Date: Tue, 17 Oct 2006 02:52:19 +0300 [thread overview]
Message-ID: <45341B33.7080801@tcs.hut.fi> (raw)
Hi,
here are a bunch of more or less related patches having to do with fixing the IPv6 routing
subtrees and source address selection. Most of the code is a cleaned up version of what
I've written earlier for MIPL 2, where it has worked pretty well for a couple of years now.
The SCTP code, however, turned out to be messier and more difficult to fix than I had
originally thought. As I'm not that familiar with SCTP and don't really have an
opportunity to test the code I'm especially grateful for any comments regarding those
parts of the code.
I've tried to split up the changes into logical parts to help digest them. Please comment!
Regards,
Ville
reply other threads:[~2006-10-16 23:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=45341B33.7080801@tcs.hut.fi \
--to=vnuorval@tcs.hut.fi \
--cc=davem@davemloft.net \
--cc=kim.nordlund@nokia.com \
--cc=lksctp-developers@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=tgraf@suug.ch \
--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).