All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antoine Tenart <antoine.tenart@free-electrons.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Antoine Tenart <antoine.tenart@free-electrons.com>,
	davem@davemloft.net, thomas.petazzoni@free-electrons.com,
	gregory.clement@free-electrons.com,
	miquel.raynal@free-electrons.com, oferh@marvell.com,
	igall@marvell.com, nadavh@marvell.com,
	linux-crypto@vger.kernel.org
Subject: Re: [PATCH 00/17] crypto: inside-secure - various improvements
Date: Fri, 22 Dec 2017 15:28:38 +0100	[thread overview]
Message-ID: <20171222142838.GB8067@kwain> (raw)
In-Reply-To: <20171222091154.GJ32542@gondor.apana.org.au>

Hi Herbert,

On Fri, Dec 22, 2017 at 08:11:54PM +1100, Herbert Xu wrote:
> On Thu, Dec 14, 2017 at 03:26:42PM +0100, Antoine Tenart wrote:
> > 
> > This series depends on the previous one, "crypto: inside-secure - set of
> > fixes"[1]. The series contains various improvements to the Inside Secure
> > SafeXcel driver, which are bundled in a single series to avoid any
> > conflict.
> > 
> > - Patches 1-4 are cosmetic fixes (typo, more comments and dead code removal).
> > - Patches 5-8 are small improvements, mostly to improve the invalidation
> >   path.
> > - Patches 9-15 improve the request processing in the driver, by moving
> >   the requests dequeing into a workqueue and the result handling into a
> >   threaded IRQ thread. Other small improvements are made in the same
> >   direction.
> > - Patches 16-17 introduce the support of another revision of this crypto
> >   engine, similar to the one already supported. This crypto engine can be
> >   found on Marvell boards. (The corresponding device tree patches will follow
> >   once this series lands in).
> 
> Patches 1-16 applied.  If patch 17 needs to go through the crypto
> tree please let me know.

Thanks! Yes patch 17 should got through the crypto tree as well.

Thanks,
Antoine

-- 
Antoine Ténart, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-12-22 14:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-14 14:26 [PATCH 00/17] crypto: inside-secure - various improvements Antoine Tenart
2017-12-14 14:26 ` [PATCH 01/17] crypto: inside-secure - remove extra empty line Antoine Tenart
2017-12-14 14:26 ` [PATCH 02/17] crypto: inside-secure - fix typo in a comment Antoine Tenart
2017-12-14 14:26 ` [PATCH 03/17] crypto: inside-secure - remove useless memset Antoine Tenart
2017-12-14 14:26 ` [PATCH 04/17] crypto: inside-secure - comment the caching function Antoine Tenart
2017-12-14 14:26 ` [PATCH 05/17] crypto: inside-secure - refrain from unneeded invalidations Antoine Tenart
2017-12-14 14:26 ` [PATCH 06/17] crypto: inside-secure - EBUSY is not an error on async request Antoine Tenart
2017-12-14 14:26 ` [PATCH 07/17] crypto: inside-secure - move cipher crypto mode to request context Antoine Tenart
2017-12-14 14:26 ` [PATCH 08/17] crypto: inside-secure - remove unused parameter in invalidate_cache Antoine Tenart
2017-12-14 14:26 ` [PATCH 09/17] crypto: inside-secure - move request dequeueing into a workqueue Antoine Tenart
2017-12-14 14:26 ` [PATCH 10/17] crypto: inside-secure - use threaded IRQs for result handling Antoine Tenart
2017-12-14 14:26 ` [PATCH 11/17] crypto: inside-secure - dequeue all requests at once Antoine Tenart
2017-12-14 14:26 ` [PATCH 12/17] crypto: inside-secure - increase the ring size Antoine Tenart
2017-12-14 14:26 ` [PATCH 13/17] crypto: inside-secure - acknowledge the result requests all at once Antoine Tenart
2017-12-14 14:26 ` [PATCH 14/17] crypto: inside-secure - handle more result requests when counter is full Antoine Tenart
2017-12-14 14:26 ` [PATCH 15/17] crypto: inside-secure - retry to proceed the request later on fail Antoine Tenart
2017-12-14 14:26 ` [PATCH 16/17] crypto: inside-secure - EIP97 support Antoine Tenart
2017-12-14 14:26 ` [PATCH 17/17] Documentation/bindings: crypto: document the SafeXcel EIP97 compatible Antoine Tenart
2017-12-22  9:11 ` [PATCH 00/17] crypto: inside-secure - various improvements Herbert Xu
2017-12-22 14:28   ` Antoine Tenart [this message]
2018-01-12 13:02     ` Antoine Tenart
2018-01-14 11:15       ` 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=20171222142838.GB8067@kwain \
    --to=antoine.tenart@free-electrons.com \
    --cc=davem@davemloft.net \
    --cc=gregory.clement@free-electrons.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=igall@marvell.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=miquel.raynal@free-electrons.com \
    --cc=nadavh@marvell.com \
    --cc=oferh@marvell.com \
    --cc=thomas.petazzoni@free-electrons.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.