All of lore.kernel.org
 help / color / mirror / Atom feed
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>,
	"linux-crypto@vger.kernel.org" <linux-crypto@vger.kernel.org>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"' David S. Miller '" <davem@davemloft.net>
Subject: Re: crypto: inside_secure - call for volunteers
Date: Tue, 30 Apr 2019 15:55:42 +0200	[thread overview]
Message-ID: <20190430135542.GC3508@kwain> (raw)
In-Reply-To: <DBBPR09MB352652D305657569DCA6E436D23A0@DBBPR09MB3526.eurprd09.prod.outlook.com>

On Tue, Apr 30, 2019 at 01:41:27PM +0000, Pascal Van Leeuwen wrote:
> >
> > I do have access to Marvell boards, having the EIP197 & EIP97 engines.
> > I
> > can help testing your modifications on those boards. Do you have a
> > public branch somewhere I can access?
> >
> I do have a git tree on Github:
> https://github.com/pvanleeuwen/linux.git
> 
> The branch I've been working on is "is_driver_armada_fix".
> 
> I don't actually know if that's publicly accessible or if I need to
> do something to make it so ... first time Git user here :-) So let me
> know if you have issues accessing that.
> 
> Alternatively, I can also send a patch file against the driver that's
> currently part of the kernel mainline Git. Or a source tarball FTM.

Thanks! Your branch is accessible, I'll be able to have a look at it.

Btw, my current development branch for the EIP driver is at:
https://github.com/atenart/linux/tree/v5.1-rc1/eip-fixes

It contains improvements & fixes for the IV retrieval and HMAC tests.
AEAD still has some issues with some testmgr tests due to the recent
refactoring.

Antoine

-- 
Antoine Ténart, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-04-30 13:55 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 [this message]
2019-05-15  9:02       ` Pascal Van Leeuwen
2019-05-27 15:00         ` antoine.tenart
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=20190430135542.GC3508@kwain \
    --to=antoine.tenart@bootlin.com \
    --cc=davem@davemloft.net \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=pvanleeuwen@insidesecure.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.