From: Thomas Graf <tgraf@suug.ch>
To: "YOSHIFUJI Hideaki / ?$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: netdev@vger.kernel.org, vnuorval@tcs.hut.fi,
usagi-core@linux-ipv6.org, davem@davemloft.net,
anttit@tcs.hut.fi
Subject: Re: [PATCHSET] Multiple IPV6 Routing Tables & Policy Routing
Date: Fri, 4 Aug 2006 19:41:20 +0200 [thread overview]
Message-ID: <20060804174120.GN14627@postel.suug.ch> (raw)
In-Reply-To: <20060805.005855.08672511.yoshfuji@linux-ipv6.org>
* YOSHIFUJI Hideaki / ?$B5HF#1QL@ <yoshfuji@linux-ipv6.org> 2006-08-05 00:58
> In article <20060804102308.711837665@postel.suug.ch> (at Fri, 04 Aug 2006 12:23:08 +0200), Thomas Graf <tgraf@suug.ch> says:
>
> > This patchset implements multiple IPv6 routing tables and
> > policy routing. Even though the code is almost rewritten
> :
>
> Thomas, there are some coflicts with current net-2.6 tree.
> Would you please sync with latest net-2.6 tree.
The patches are against the net-2.6.19 tree.
next prev parent reply other threads:[~2006-08-04 17:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 10:23 [PATCHSET] Multiple IPV6 Routing Tables & Policy Routing Thomas Graf
2006-08-03 22:00 ` [PATCH 1/5] [IPV6]: Remove ndiscs rt6_lock dependency Thomas Graf
2006-08-03 22:00 ` [PATCH 2/5] [IPV6]: Multiple Routing Tables Thomas Graf
2006-08-05 9:00 ` Patrick McHardy
2006-08-05 9:21 ` David Miller
2006-08-03 22:00 ` [PATCH 3/5] [NET]: Protocol Independant Policy Routing Rules Framework Thomas Graf
2006-08-03 22:00 ` [PATCH 4/5] [IPV6]: Policy Routing Rules Thomas Graf
2006-08-03 22:00 ` [PATCH 5/5] [IPV4]: Use Protocol Independant Policy Routing Rules Framework Thomas Graf
2006-08-04 10:40 ` [PATCHSET] Multiple IPV6 Routing Tables & Policy Routing David Miller
2006-08-04 15:58 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-04 17:41 ` Thomas Graf [this message]
2006-08-04 18:14 ` YOSHIFUJI Hideaki / 吉藤英明
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=20060804174120.GN14627@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=anttit@tcs.hut.fi \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=usagi-core@linux-ipv6.org \
--cc=vnuorval@tcs.hut.fi \
--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).