From: "antoine.tenart@bootlin.com" <antoine.tenart@bootlin.com>
To: Pascal Van Leeuwen <pvanleeuwen@insidesecure.com>
Cc: "antoine.tenart@bootlin.com" <antoine.tenart@bootlin.com>,
Riku Voipio <riku.voipio@linaro.org>,
"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>
Subject: Re: crypto: inside_secure - call for volunteers
Date: Mon, 27 May 2019 17:00:58 +0200 [thread overview]
Message-ID: <20190527150057.GD8900@kwain> (raw)
In-Reply-To: <AM6PR09MB3523E393D4EA082FDDBC9251D2090@AM6PR09MB3523.eurprd09.prod.outlook.com>
Hi Pascal,
On Wed, May 15, 2019 at 09:02:42AM +0000, Pascal Van Leeuwen wrote:
>
> It's been 2 weeks already so I'm kind of curious if either one of you
> managed to try anything with my modified Inside Secure driver yet?
> Note that if you experience any issues at all that:
>
> a) I'd be very interested to hear about them
> b) I'm fully willing to help resolve those issues
>
> BTW: if there are no issues and everything worked fine I'm also
> interested to hear about that :-)
Sorry about the looong delay. I did make a quick test of your series and
had some issues:
- You added use of PCI helpers, but this new dependency wasn't described
in Kconfig (leading to have build issues).
- Using an EIP197 and a MacchiatoBin many of the boot tests did not
pass (but I haven't look into it).
I'll perform the test again to at least give you a trace :)
Btw, I'm available on IRC (atenart on Freenode), that might be easier to
have a discussion when debugging things.
Thanks!
Antoine
--
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-05-27 15:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 13:08 crypto: inside_secure - call for volunteers Pascal Van Leeuwen
2019-04-30 13:26 ` antoine.tenart
2019-04-30 13:41 ` Pascal Van Leeuwen
2019-04-30 13:55 ` antoine.tenart
2019-05-15 9:02 ` Pascal Van Leeuwen
2019-05-27 15:00 ` antoine.tenart [this message]
2019-05-27 21:06 ` Pascal Van Leeuwen
2019-05-28 12:45 ` antoine.tenart
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=20190527150057.GD8900@kwain \
--to=antoine.tenart@bootlin.com \
--cc=linux-crypto@vger.kernel.org \
--cc=pvanleeuwen@insidesecure.com \
--cc=riku.voipio@linaro.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).