From: "David S. Miller" <davem@redhat.com>
To: kazunori@miyazawa.org
Cc: kuznet@ms2.inr.ac.ru, linux-kernel@vger.kernel.org,
netdev@oss.sgi.com, usagi-core@linux-ipv6.org,
kunihiro@ipinfusion.com
Subject: Re: [PATCH] IPv6 IPSEC support
Date: Sat, 22 Feb 2003 03:13:26 -0800 (PST) [thread overview]
Message-ID: <20030222.031326.103246837.davem@redhat.com> (raw)
In-Reply-To: <20030222202623.38d41d8a.kazunori@miyazawa.org>
From: Kazunori Miyazawa <kazunori@miyazawa.org>
Date: Sat, 22 Feb 2003 20:26:23 +0900
I also moved the functions for ah, and esp.
I don't think this is so good idea...
As a result of moving IPv6 IPsec functions to net/ipv4, it currently prevents to
make IPv6 as a module.
This is one of the reasons why ah/esp ipv6 should stay under ipv6.
Nothing in xfrm routines really need to reference ipv6 module
functions, please eliminate this dependency. Breaking ipv6 as module
is ok for temporary development, but eventually it must be solved.
next prev parent reply other threads:[~2003-02-22 11:13 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-22 11:26 [PATCH] IPv6 IPSEC support Kazunori Miyazawa
2003-02-22 11:13 ` David S. Miller [this message]
2003-02-22 12:15 ` Kazunori Miyazawa
2003-02-22 12:49 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-22 23:47 ` David S. Miller
2003-02-23 0:44 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-23 15:35 ` Kazunori Miyazawa
-- strict thread matches above, loose matches on Subject: below --
2003-02-19 4:48 [PATCH] IPv6 IPsec support Kazunori MIyazawa
2003-02-19 4:50 ` David S. Miller
2003-02-19 5:10 ` Kunihiro Ishiguro
2003-02-19 5:17 ` Mitsuru KANDA / 神田 充
2003-02-19 5:58 ` Kazunori Miyazawa
2003-02-19 5:30 ` YOSHIFUJI Hideaki / 吉藤英明
2003-02-19 5:57 ` Kunihiro Ishiguro
2003-02-19 7:02 ` David S. Miller
2003-02-19 9:13 ` Kunihiro Ishiguro
2003-02-19 7:13 ` David S. Miller
2003-02-19 7:33 ` David S. Miller
2003-02-19 16:56 ` Mitsuru KANDA / 神田 充
2003-02-19 21:43 ` David S. Miller
2003-02-19 23:10 ` Kunihiro Ishiguro
2003-02-20 0:37 ` David S. 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=20030222.031326.103246837.davem@redhat.com \
--to=davem@redhat.com \
--cc=kazunori@miyazawa.org \
--cc=kunihiro@ipinfusion.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=usagi-core@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).