From: Masahide NAKAMURA <nakam@linux-ipv6.org>
To: Ingo Oeser <netdev@axxeo.de>
Cc: davem@davemloft.net, netdev@vger.kernel.org, herbert@gondor.apana.org.au
Subject: Re: [PATCH 2/2] [IPV6] MIP6: Loadable module support for MIPv6.
Date: Thu, 24 May 2007 10:48:27 +0900 [thread overview]
Message-ID: <4654EEEB.1030603@linux-ipv6.org> (raw)
In-Reply-To: <200705231154.33208.netdev@axxeo.de>
Ingo Oeser wrote:
> nakam@linux-ipv6.org schrieb:
>> From: Masahide NAKAMURA <nakam@linux-ipv6.org>
>>
>> This patch makes MIPv6 loadable module named "mip6".
>>
>> Here is a modprobe.conf(5) example to load it automatically
>> when user application uses XFRM state for MIPv6:
>>
>> alias xfrm-type-10-43 mip6
>> alias xfrm-type-10-60 mip6
>
> What about MODULE_ALIAS("xfrm-type-10-60")
> and MODULE_ALIAS("xfrm-type-10-43") in mip6.c ?
>
> The aliases in modprobe.conf(5) should not be necessary then.
>
> If you are really ambitious you can even define a
> MODULE_ALIAS_XFRM_TYPE macro in include/net/xfrm.h
> simliar to to MODULE_ALIAS_XFRM_MODE.
I prefer to use new macro like XFRM mode to unify XFRM
protocols i.e. esp[46].c, ah[46].c, ipcomp[46].c, and mip6.c
if we care about it. Can I add it as extensional patch
if nobody has a plan to do this yet?
> Please be sure to discuss CC Herbert Xu then.
# CC-ed.
Regards,
--
Masahide NAKAMURA
next prev parent reply other threads:[~2007-05-24 1:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-23 7:50 [PATCH 2/2] [IPV6] MIP6: Loadable module support for MIPv6 nakam
2007-05-23 9:54 ` Ingo Oeser
2007-05-24 1:48 ` Masahide NAKAMURA [this message]
2007-05-24 8:36 ` Ingo Oeser
2007-05-24 13:23 ` Masahide NAKAMURA
2007-05-24 8:36 ` Herbert Xu
2007-06-27 6:56 ` 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=4654EEEB.1030603@linux-ipv6.org \
--to=nakam@linux-ipv6.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@axxeo.de \
--cc=netdev@vger.kernel.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).