From: Li Yewang <lyw@cn.fujitsu.com>
To: netdev-owner@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: [patch][ipsec] can not add camellia cipher algorithm when using "ip xfrm state" command
Date: Mon, 30 Nov 2009 09:39:29 +0800 [thread overview]
Message-ID: <4B132251.5060806@cn.fujitsu.com> (raw)
can not add camellia cipher algorithm when using "ip xfrm state" command.
Signed-off-by: Li Yewang <lyw@cn.fujitsu.com>
---
net/xfrm/xfrm_algo.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/net/xfrm/xfrm_algo.c b/net/xfrm/xfrm_algo.c
index faf54c6..348196d 100644
--- a/net/xfrm/xfrm_algo.c
+++ b/net/xfrm/xfrm_algo.c
@@ -365,6 +365,7 @@ static struct xfrm_algo_desc ealg_list[] = {
},
{
.name = "cbc(camellia)",
+ .compat = "camellia",
.uinfo = {
.encr = {
--
1.6.4.1
next reply other threads:[~2009-11-30 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-30 1:39 Li Yewang [this message]
2009-12-01 23:35 ` [patch][ipsec] can not add camellia cipher algorithm when using "ip xfrm state" command 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=4B132251.5060806@cn.fujitsu.com \
--to=lyw@cn.fujitsu.com \
--cc=netdev-owner@vger.kernel.org \
--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).