From: Jussi Kivilinna <jussi.kivilinna@iki.fi>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: linux-crypto@vger.kernel.org, netdev@vger.kernel.org,
Tom St Denis <tstdenis@elliptictech.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/2] crypto: add CMAC support to CryptoAPI
Date: Mon, 08 Apr 2013 12:31:24 +0300 [thread overview]
Message-ID: <51628E6C.1050600@iki.fi> (raw)
In-Reply-To: <20130408082416.GW21448@secunet.com>
On 08.04.2013 11:24, Steffen Klassert wrote:
> On Mon, Apr 08, 2013 at 10:48:44AM +0300, Jussi Kivilinna wrote:
>> Patch adds support for NIST recommended block cipher mode CMAC to CryptoAPI.
>>
>> This work is based on Tom St Denis' earlier patch,
>> http://marc.info/?l=linux-crypto-vger&m=135877306305466&w=2
>>
>> Cc: Tom St Denis <tstdenis@elliptictech.com>
>> Signed-off-by: Jussi Kivilinna <jussi.kivilinna@iki.fi>
>
> This patch does not apply clean to the ipsec-next tree
> because of some crypto changes I don't have in ipsec-next.
> The IPsec part should apply to the cryptodev tree,
> so it's probaply the best if we route this patchset
> through the cryptodev tree.
I should have mentioned that the patchset is on top of cryptodev tree and
previous crypto patches that I send yesterday, likely to cause problems
atleast at tcrypt.c:
http://marc.info/?l=linux-crypto-vger&m=136534223503368&w=2
-Jussi
>
> Herbert,
>
> are you going to take these patches?
>
next prev parent reply other threads:[~2013-04-08 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-08 7:48 [PATCH 1/2] crypto: add CMAC support to CryptoAPI Jussi Kivilinna
2013-04-08 7:48 ` [PATCH 2/2] xfrm: add rfc4494 AES-CMAC-96 support Jussi Kivilinna
2013-04-08 8:24 ` [PATCH 1/2] crypto: add CMAC support to CryptoAPI Steffen Klassert
2013-04-08 9:31 ` Jussi Kivilinna [this message]
2013-04-08 9:33 ` Herbert Xu
2013-04-08 20:49 ` David Miller
[not found] ` <CADT32eLHBWoRMvnBWbEEEWfpQtsnivYSeSgyG95MhURVEgmgjA@mail.gmail.com>
2013-04-08 13:20 ` Steve French
2013-04-10 3:32 ` Herbert Xu
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=51628E6C.1050600@iki.fi \
--to=jussi.kivilinna@iki.fi \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
--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).