From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: David Miller <davem@davemloft.net>
Cc: yoshfuji@linux-ipv6.org, anttit@tcs.hut.fi, vnuorval@tcs.hut.fi,
netdev@vger.kernel.org, usagi-core@linux-ipv6.org
Subject: Re: [PATCH 0/20][IPV6/XFRM] MIPv6 CN (part B)
Date: Wed, 02 Aug 2006 17:26:12 +0900 [thread overview]
Message-ID: <44D061A4.8050807@linux-ipv6.org> (raw)
In-Reply-To: <20060801.173051.35665426.davem@davemloft.net>
David Miller wrote:
> From: Masahide NAKAMURA <nakam@linux-ipv6.org>
> Date: Sat, 29 Jul 2006 18:37:04 +0900
>
>> Here is Part B patches, following this mail.
>>
>> Part B is also available as mip6cn-20060716-review branch at:
>>
>> git://git.skbuff.net:9419/gitroot/nakam/linux-2.6-mip6cn
>>
>> This tree includes part A, then it has all patches about
>> "Advanced XFRM for CN".
>
> These patches mainly deal with the specifics of ipv6
> mobility processing, they look mostly fine to me and
> I could not spot any obvious errors.
Thank you for reviewing.
Next time I prepare the patch for the latest tree
with fixes about comments.
Thanks,
--
Masahide NAKAMURA
next prev parent reply other threads:[~2006-08-02 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-29 9:23 [RFC] Mobile IPv6 introduction Masahide NAKAMURA
2006-07-29 9:28 ` [PATCH 0/23][XFRM] MIPv6 CN introduction (part A) (Re: [RFC] Mobile IPv6 introduction) Masahide NAKAMURA
2006-07-29 9:37 ` [PATCH 0/20][IPV6/XFRM] MIPv6 CN (part B) Masahide NAKAMURA
2006-08-02 0:30 ` David Miller
2006-08-02 8:26 ` Masahide NAKAMURA [this message]
2006-07-29 14:12 ` [RFC] Mobile IPv6 introduction Hugo Santos
2006-08-02 0:35 ` David Miller
2006-08-02 0:58 ` Hugo Santos
2006-08-02 1:04 ` David Miller
2006-08-02 1:52 ` YOSHIFUJI Hideaki / 吉藤英明
2006-08-02 7:58 ` Ville Nuorvala
2006-08-02 11:03 ` Hugo Santos
2006-08-02 3:24 ` Masahide NAKAMURA
2006-08-02 10:47 ` Hugo Santos
2006-08-02 13:03 ` Masahide NAKAMURA
2006-08-02 21:14 ` 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=44D061A4.8050807@linux-ipv6.org \
--to=nakam@linux-ipv6.org \
--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).