From: Philippe REYNES <philippe.reynes@softathome.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V2 4/4] pytest: aes: add test for aes192 and aes256
Date: Thu, 31 Oct 2019 14:33:11 +0100 (CET) [thread overview]
Message-ID: <2012146541.1132041.1572528791781.JavaMail.zimbra@softathome.com> (raw)
In-Reply-To: <CAPnjgZ31E5JYZ5w8bsPu1sJ2pXYCXTLVd4ncC4fkL=M4vp8Wuw@mail.gmail.com>
Hi Simonn
> Hi Philippe,
>
> On Tue, 29 Oct 2019 at 11:29, Philippe Reynes
> <philippe.reynes@softathome.com> wrote:
>>
>> This commit update the aes tests to check the
>> aes192 and aes256.
>>
>> Signed-off-by: Philippe Reynes <philippe.reynes@softathome.com>
>> ---
>> test/py/tests/test_aes.py | 118 +++++++++++++++++++++++++++++++++++-----------
>> 1 file changed, 91 insertions(+), 27 deletions(-)
>
> Any way we could write these tests in C?
I'm not sure to understand. Do you mean
- write this code in C and then call it from python (in pytest) ?
- write this test in C to implement a ut command (like UT_TIME) ?
>>
>> Changelog:
>> v2:
>> - add a really simple commit text
>> - re-write the test with the new version of test for aes128
>> - add a test to check that results of aes128/192/256 are differents
>
>
> Regards,
> SImon
Regards,
Philippe
next prev parent reply other threads:[~2019-10-31 13:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-29 17:29 [U-Boot] [PATCH V2 0/4] aes: add support for aes192 and aes256 Philippe Reynes
2019-10-29 17:29 ` [U-Boot] [PATCH V2 1/4] aes: add a define for the size of a block Philippe Reynes
2019-10-30 1:48 ` Simon Glass
2019-10-29 17:29 ` [U-Boot] [PATCH V2 2/4] aes: add support of aes192 and aes256 Philippe Reynes
2019-10-30 1:49 ` Simon Glass
2019-10-29 17:29 ` [U-Boot] [PATCH V2 3/4] tegra20: crypto: update code to use new aes api Philippe Reynes
2019-10-30 1:48 ` Simon Glass
2019-10-29 17:29 ` [U-Boot] [PATCH V2 4/4] pytest: aes: add test for aes192 and aes256 Philippe Reynes
2019-10-30 1:49 ` Simon Glass
2019-10-31 13:33 ` Philippe REYNES [this message]
2019-12-10 15:18 ` Simon Glass
2020-01-06 10:51 ` Philippe REYNES
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=2012146541.1132041.1572528791781.JavaMail.zimbra@softathome.com \
--to=philippe.reynes@softathome.com \
--cc=u-boot@lists.denx.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