From: Tom St Denis <tstdenis@elliptictech.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: linux-kernel@vger.kernel.org, davem@davemloft.net,
herbert@gondor.hengli.com.au
Subject: Re: [PATCH] Added NIST CMAC to the CryptoAPI library
Date: Tue, 8 Jan 2013 05:59:30 -0500 (EST) [thread overview]
Message-ID: <1423338194.36510.1357642769950.JavaMail.root@elliptictech.com> (raw)
In-Reply-To: <20130108085425.GU18940@secunet.com>
Hi all,
I agree with the ^ comment ... I'll look into the "styles" issue, though ironically I would consider that a maintainers job...
I'll resend a bit later today.
Tom
----- Original Message -----
> From: "Steffen Klassert" <steffen.klassert@secunet.com>
> To: "Tom St Denis" <tstdenis@elliptictech.com>
> Cc: linux-kernel@vger.kernel.org, davem@davemloft.net, herbert@gondor.apana.org.au
> Sent: Tuesday, 8 January, 2013 3:54:25 AM
> Subject: Re: [PATCH] Added NIST CMAC to the CryptoAPI library
>
> On Tue, Dec 11, 2012 at 02:00:10PM -0500, Tom St Denis wrote:
> > This patch adds NIST CMAC cipher based MAC as described in FIPS
> > 800-38B to
> > the CryptoAPI stack. It also wires up the MAC to the IPsec stack
> > as per
> > RFC 4494.
> >
> > This patch was tested against 3.7 with third party hardware IPsec.
> >
> > Signed-off-by: Tom St Denis <tstdenis@elliptictech.com>
> > Acked-by: David S. Miller <davem@davemloft.net>
> >
>
> I agreed with Herbert Xu to integrate this via the ipsec-next tree.
>
> However, it introduces the following warning:
>
> crypto/cmac.c: In function ‘crypto_cmac_digest_setkey’:
> crypto/cmac.c:97:4: warning: suggest parentheses around arithmetic in
> operand of ‘^’ [-Wparentheses]
>
> It also has a lot of coding style issues, run checkpatch.
>
> Please fix it and resend.
>
> Thanks!
>
next prev parent reply other threads:[~2013-01-08 10:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1068116509.71782.1353434081056.JavaMail.root@elliptictech.com>
2012-12-11 19:00 ` [PATCH] Added NIST CMAC to the CryptoAPI library Tom St Denis
2013-01-08 8:54 ` Steffen Klassert
2013-01-08 10:59 ` Tom St Denis [this message]
2012-11-20 15:24 Tom St Denis
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=1423338194.36510.1357642769950.JavaMail.root@elliptictech.com \
--to=tstdenis@elliptictech.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.hengli.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=steffen.klassert@secunet.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