mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 0/7 v2] digest: allow multiple implementation of digest
Date: Wed, 25 Mar 2015 19:44:43 +0800	[thread overview]
Message-ID: <339AF302-AF56-4794-92B7-0022D3FEEAE9@jcrosoft.com> (raw)
In-Reply-To: <20150325102635.GD9742@pengutronix.de>


> On Mar 25, 2015, at 6:26 PM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
> 
> On Tue, Mar 24, 2015 at 02:00:35PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> Hi,
>> 
>> 	The following serie allow you to have multiple driver for
>> 	the digest.
>> 
>> 	This also switch the sha1 implementation to the kernel one and
>> 	add the armv4 asm implementtion that save nearly 6KiB in a zbarebox
>> 	lzo.
>> 
>> 
>> v2:
>> 	switch sha256 and sha512 to linux implementation
>> 	add arm sha256 asm implementation
>> 
>> The following changes since commit 52d4a0321405b7525422f04fffbe7f318c9c5a88:
>> 
>>  Merge branch 'for-next/state' into next (2015-03-19 07:55:59 +0100)
>> 
>> are available in the git repository at:
>> 
>>  git://git.jcrosoft.org/barebox.git delivery/sha1
>> 
>> for you to fetch changes up to 6bebe62f4b828f0b85334b8a8a189e8a84864935:
>> 
>>  arm: crypto: add sha256 assembly support (2015-03-24 17:18:55 +0800)
> 
> Except for the one comment I made the series looks fine.

I found a bug in the sha256 asm code we discuss it on the arm ML with a fix
I’ll integrate it

and I found an other bug that the hmac will register multiple instance of itself
for each shaxxx algo, but will always use the best shaxxx at runtime

So it’ll send a v3 for those fix

Best Regards,
J.
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

      reply	other threads:[~2015-03-25 11:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 13:00 Jean-Christophe PLAGNIOL-VILLARD
2015-03-24 13:08 ` [PATCH 1/7] command: digest: only set the key when specified Jean-Christophe PLAGNIOL-VILLARD
2015-03-24 13:08   ` [PATCH 2/7] crypto: prepare to allow multiple digest driver Jean-Christophe PLAGNIOL-VILLARD
2015-03-24 13:08   ` [PATCH 3/7] crypto: sha1: switch to linux implementation Jean-Christophe PLAGNIOL-VILLARD
2015-03-25  9:06     ` Sascha Hauer
2015-03-24 13:08   ` [PATCH 4/7] crypto: sha256: " Jean-Christophe PLAGNIOL-VILLARD
2015-03-24 13:08   ` [PATCH 5/7] crypto: sha512: " Jean-Christophe PLAGNIOL-VILLARD
2015-03-24 13:08   ` [PATCH 6/7] arm: crypto: add sha1 assembly support Jean-Christophe PLAGNIOL-VILLARD
2015-03-24 13:08   ` [PATCH 7/7] arm: crypto: add sha256 " Jean-Christophe PLAGNIOL-VILLARD
2015-03-25  2:55 ` [PATCH 0/7 v2] digest: allow multiple implementation of digest Jean-Christophe PLAGNIOL-VILLARD
2015-03-25 10:26 ` Sascha Hauer
2015-03-25 11:44   ` Jean-Christophe PLAGNIOL-VILLARD [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=339AF302-AF56-4794-92B7-0022D3FEEAE9@jcrosoft.com \
    --to=plagnioj@jcrosoft.com \
    --cc=barebox@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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