From: ebiggers@google.com (Eric Biggers)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/6] crypto: testmgr - avoid overlap in chunked tests
Date: Wed, 7 Dec 2016 12:23:46 -0800 [thread overview]
Message-ID: <20161207202346.GB125037@google.com> (raw)
In-Reply-To: <CAKv+Gu_HUjCparJnZXzZR=m3obt+aypibpHrP_ivA==1QNYksg@mail.gmail.com>
On Wed, Dec 07, 2016 at 07:53:51PM +0000, Ard Biesheuvel wrote:
> Does this help at all?
>
> diff --git a/crypto/testmgr.c b/crypto/testmgr.c
> index 670893bcf361..59e67f5b544b 100644
> --- a/crypto/testmgr.c
> +++ b/crypto/testmgr.c
> @@ -63,7 +63,7 @@ int alg_test(const char *driver, const char *alg,
> u32 type, u32 mask)
> */
> #define IDX1 32
> #define IDX2 32400
> -#define IDX3 511
> +#define IDX3 1511
> #define IDX4 8193
> #define IDX5 22222
> #define IDX6 17101
>
Yes, with that change made the self-tests pass.
Eric
next prev parent reply other threads:[~2016-12-07 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-05 18:42 [PATCH v3 0/6] crypto: ARM/arm64 CRC-T10DIF/CRC32/CRC32C roundup Ard Biesheuvel
2016-12-05 18:42 ` [PATCH v3 1/6] crypto: testmgr - avoid overlap in chunked tests Ard Biesheuvel
2016-12-07 19:19 ` Eric Biggers
2016-12-07 19:53 ` Ard Biesheuvel
2016-12-07 20:23 ` Eric Biggers [this message]
2016-12-05 18:42 ` [PATCH v3 2/6] crypto: testmgr - add/enhance test cases for CRC-T10DIF Ard Biesheuvel
2016-12-05 18:42 ` [PATCH v3 3/6] crypto: arm64/crct10dif - port x86 SSE implementation to arm64 Ard Biesheuvel
2016-12-05 18:42 ` [PATCH v3 4/6] crypto: arm/crct10dif - port x86 SSE implementation to ARM Ard Biesheuvel
2016-12-05 18:42 ` [PATCH v3 5/6] crypto: arm64/crc32 - accelerated support based on x86 SSE implementation Ard Biesheuvel
2016-12-05 18:42 ` [PATCH v3 6/6] crypto: arm/crc32 " Ard Biesheuvel
2016-12-07 12:09 ` [PATCH v3 0/6] crypto: ARM/arm64 CRC-T10DIF/CRC32/CRC32C roundup 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=20161207202346.GB125037@google.com \
--to=ebiggers@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).