From: Eric Biggers <ebiggers@kernel.org>
To: wenyehai <wenyehai@huawei.com>
Cc: "ltp@lists.linux.it" <ltp@lists.linux.it>
Subject: Re: [LTP] 答复: 答复: [PATCH] add several hash algorithms for crypto/crypto_user02.c
Date: Mon, 10 Jan 2022 19:03:13 -0800 [thread overview]
Message-ID: <YdzzcTlQpn+BNRsi@sol.localdomain> (raw)
In-Reply-To: <15b7314d82b547e997c0caca1ae1299c@huawei.com>
On Tue, Jan 11, 2022 at 02:19:05AM +0000, wenyehai wrote:
>
> Hi Eric:
>
> Thank you very much for your kind reply, and also sorry for causing you confusion.
> Actually, I do want to get crypto_user02 to run in more cases.
>
> The product which I tested just only enable sha3 algorithm, but when I run cryto_user02, it tells "no viable algorithm found", as follows:
> ./crypto_user02
> tst_test.c:1365: TINFO: Timeout per run is 0h 05m 00s
> crypto_user02.c:84: TCONF: No viable algorithm found
>
> Summary:
> passed 0
> failed 0
> broken 0
> skipped 1
> warnings 0
>
>
> I want crypto_user02 to support more cases(not only sha3), but I am not sure which algorithms should list,
> so I compare with the latest linux kernel encryption module, add several hash algorithms which not list in crypto_user02.
Okay, can you please properly explain this in your commit message?
Thanks!
- Eric
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-01-11 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 9:15 [LTP] [PATCH] add several hash algorithms for crypto/crypto_user02.c wenyehai via ltp
2022-01-05 15:13 ` Eric Biggers
2022-01-10 3:59 ` [LTP] 答复: " wenyehai via ltp
2022-01-10 17:44 ` Eric Biggers
2022-01-11 2:19 ` [LTP] 答复: " wenyehai via ltp
2022-01-11 3:03 ` Eric Biggers [this message]
2022-01-11 3:11 ` [LTP] 答复: " wenyehai via ltp
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=YdzzcTlQpn+BNRsi@sol.localdomain \
--to=ebiggers@kernel.org \
--cc=ltp@lists.linux.it \
--cc=wenyehai@huawei.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