From: Steffen Klassert <steffen.klassert@secunet.com>
To: Jussi Kivilinna <jussi.kivilinna@mbnet.fi>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
Tom St Denis <tstdenis@elliptictech.com>,
David Miller <davem@davemloft.net>
Subject: Re: [PATCH] CMAC support for CryptoAPI, fixed patch issues, indent, and testmgr build issues
Date: Tue, 29 Jan 2013 10:33:31 +0100 [thread overview]
Message-ID: <20130129093331.GA23291@secunet.com> (raw)
In-Reply-To: <20130124112410.8535.75598.stgit@localhost6.localdomain6>
On Thu, Jan 24, 2013 at 01:25:46PM +0200, Jussi Kivilinna wrote:
>
> Maybe it would be cleaner to not mess with pfkeyv2.h at all, but instead mark algorithms that do not support pfkey with flag. See patch below.
>
As nobody seems to have another opinion, we could go either with your
approach, or we can invert the logic and mark all existing algorithms
as pfkey supported. Then we would not need to bother about pfkey again.
I'd be fine with both. Do you want to submit a patch?
next prev parent reply other threads:[~2013-01-29 9:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <537355069.94465.1358772395763.JavaMail.root@elliptictech.com>
[not found] ` <436404741.94502.1358773048618.JavaMail.root@elliptictech.com>
2013-01-21 16:40 ` [PATCH] CMAC support for CryptoAPI, fixed patch issues, indent, and testmgr build issues David Dillow
2013-01-23 7:41 ` Steffen Klassert
2013-01-23 14:36 ` Jussi Kivilinna
2013-01-23 14:46 ` Tom St Denis
2013-01-23 15:35 ` Jussi Kivilinna
2013-01-23 15:46 ` Tom St Denis
2013-01-23 16:16 ` YOSHIFUJI Hideaki
2013-01-23 16:25 ` YOSHIFUJI Hideaki
2013-01-24 8:45 ` Jussi Kivilinna
2013-01-24 9:43 ` Steffen Klassert
2013-01-24 11:25 ` Jussi Kivilinna
2013-01-24 12:32 ` Steffen Klassert
2013-01-24 12:37 ` Tom St Denis
2013-01-24 12:52 ` Steffen Klassert
2013-01-24 13:00 ` Tom St Denis
2013-01-29 9:33 ` Steffen Klassert [this message]
2013-01-31 9:35 ` Jussi Kivilinna
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=20130129093331.GA23291@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=jussi.kivilinna@mbnet.fi \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tstdenis@elliptictech.com \
/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).