Which algorithm (apart from crc* which I know and will fix) uses the
same driver name as its algorithm name? Doing this will cause issues
when an alternative implementation for that algorithm gets added.
Fixing names resolves double calls only for the thread cryptomgr_test-alg_test
where the
Horia Ioan-B05471; Stoica Cristian-
B18196
Subject: [PATCH] crypto: remove double execution of the same test suite
This patch removes redundant execution of the same test suite in cases
where alg and driver variables are the same (e.g. when alg_test is
called from tcrypt_test)
Signed-off
On Thu, Jul 18, 2013 at 06:57:07PM +0300, Cristian Stoica wrote:
This patch removes redundant execution of the same test suite in cases
where alg and driver variables are the same (e.g. when alg_test is
called from tcrypt_test)
Signed-off-by: Cristian Stoica cristian.sto...@freescale.com
On 7/18/2013 6:57 PM, Cristian Stoica wrote:
This patch removes redundant execution of the same test suite in cases
where alg and driver variables are the same (e.g. when alg_test is
called from tcrypt_test)
Signed-off-by: Cristian Stoica cristian.sto...@freescale.com
Reviewed-by: Horia
This patch removes redundant execution of the same test suite in cases
where alg and driver variables are the same (e.g. when alg_test is
called from tcrypt_test)
Signed-off-by: Cristian Stoica cristian.sto...@freescale.com
---
crypto/testmgr.c | 2 +-
1 file changed, 1 insertion(+), 1