netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shinta@sfc.wide.ad.jp
Cc: netdev@vger.kernel.org, Francis.Dupont@point6.net,
	nakam@linux-ipv6.org, yoshfuji@linux-ipv6.org,
	usagi-core@linux-ipv6.org
Subject: Re: [PATCH 0/5] [XFRM,PFKEYV2]: MIGRATE support (take 3)
Date: Thu, 08 Feb 2007 13:32:24 -0800 (PST)	[thread overview]
Message-ID: <20070208.133224.41636066.davem@davemloft.net> (raw)
In-Reply-To: <20070208113221.193F.SHINTA@sfc.wide.ad.jp>

From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
Date: Thu, 08 Feb 2007 12:09:29 +0900

> The patch set consists of following 5 patches:
> 
> [PATCH (1/5)] [XFRM]: Extension for dynamic update of endpoint address(es)
> [PATCH (2/5)] [XFRM]: User interface for handling XFRM_MSG_MIGRATE
> [PATCH (3/5)] [XFRM]: CONFIG_XFRM_MIGRATE option
> [PATCH (4/5)] [PFKEYV2]: Extension for dynamic update of endpoint address(es)
> [PATCH (5/5)] [PFKEYV2]: CONFIG_NET_KEY_MIGRATE option
> 
> And it can also be fetched by git from following repository with
> branch name "migrate-take3".

Patch applied, but I had to add the following bug fix in
order to fix xfrm_user and af_key when built as modules.

commit e610e679dd0057403c96cd31f8739792780732ee
Author: David S. Miller <davem@sunset.davemloft.net>
Date:   Thu Feb 8 13:29:15 2007 -0800

    [XFRM]: xfrm_migrate() needs exporting to modules.
    
    Needed by xfrm_user and af_key.
    
    Signed-off-by: David S. Miller <davem@davemloft.net>

diff --git a/net/xfrm/xfrm_policy.c b/net/xfrm/xfrm_policy.c
index 825c60a..fa7ce06 100644
--- a/net/xfrm/xfrm_policy.c
+++ b/net/xfrm/xfrm_policy.c
@@ -2464,5 +2464,6 @@ restore_state:
 
 	return err;
 }
+EXPORT_SYMBOL(xfrm_migrate);
 #endif
 

      reply	other threads:[~2007-02-08 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08  3:09 [PATCH 0/5] [XFRM,PFKEYV2]: MIGRATE support (take 3) Shinta Sugimoto
2007-02-08 21:32 ` David Miller [this message]

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=20070208.133224.41636066.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=Francis.Dupont@point6.net \
    --cc=nakam@linux-ipv6.org \
    --cc=netdev@vger.kernel.org \
    --cc=shinta@sfc.wide.ad.jp \
    --cc=usagi-core@linux-ipv6.org \
    --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).