From: Steffen Klassert <steffen.klassert@secunet.com>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: [PATCH] pf_key/xfrm_algo: prepare pf_key and xfrm_algo for new algorithms without pfkey support
Date: Mon, 4 Feb 2013 09:09:14 +0100 [thread overview]
Message-ID: <20130204080914.GC23291@secunet.com> (raw)
In-Reply-To: <20130131104038.6852.57446.stgit@localhost6.localdomain6>
On Thu, Jan 31, 2013 at 12:40:38PM +0200, Jussi Kivilinna wrote:
> Mark existing algorithms as pfkey supported and make pfkey only use algorithms
> that have pfkey_supported set.
>
> Signed-off-by: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Applied to ipsec-next.
Thanks a lot Jussi!
prev parent reply other threads:[~2013-02-04 8:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 10:40 [PATCH] pf_key/xfrm_algo: prepare pf_key and xfrm_algo for new algorithms without pfkey support Jussi Kivilinna
2013-02-04 8:09 ` Steffen Klassert [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=20130204080914.GC23291@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jussi.kivilinna@mbnet.fi \
--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).