linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Gilad Ben-Yossef <gilad@benyossef.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Ofir Drang <ofir.drang@arm.com>,
	linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] cleanups and new HW rev support
Date: Sat, 3 Mar 2018 00:42:12 +0800	[thread overview]
Message-ID: <20180302164212.GE21579@gondor.apana.org.au> (raw)
In-Reply-To: <1519051887-4668-1-git-send-email-gilad@benyossef.com>

On Mon, Feb 19, 2018 at 02:51:20PM +0000, Gilad Ben-Yossef wrote:
> This patch set introduces backward compatible support for the older
> CryptoCell hardware revision 710 and 630 along some minor code
> cleanups.
> 
> Gilad Ben-Yossef (4):
>   crypto: ccree: remove unused definitions
>   dt-bindings: Add DT bindings for ccree 710 and 630p
>   crypto: ccree: add support for older HW revs
>   crypto: ccree: replace memset+kfree with kzfree
> 
>  .../devicetree/bindings/crypto/arm-cryptocell.txt  |   3 +-
>  drivers/crypto/Kconfig                             |   6 +-
>  drivers/crypto/ccree/cc_aead.c                     |  34 +++--
>  drivers/crypto/ccree/cc_cipher.c                   |  25 +++-
>  drivers/crypto/ccree/cc_crypto_ctx.h               |  36 -----
>  drivers/crypto/ccree/cc_driver.c                   |  68 ++++++++--
>  drivers/crypto/ccree/cc_driver.h                   |  23 +++-
>  drivers/crypto/ccree/cc_fips.c                     |  13 +-
>  drivers/crypto/ccree/cc_hash.c                     | 149 +++++++++++----------
>  drivers/crypto/ccree/cc_hash.h                     |  12 +-
>  drivers/crypto/ccree/cc_host_regs.h                |   3 +
>  drivers/crypto/ccree/cc_hw_queue_defs.h            |   2 +-
>  drivers/crypto/ccree/cc_kernel_regs.h              |   1 +
>  drivers/crypto/ccree/cc_request_mgr.c              |   9 +-
>  drivers/crypto/ccree/cc_sram_mgr.c                 |  14 ++
>  15 files changed, 240 insertions(+), 158 deletions(-)

All applied.  Thanks.
-- 
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt

      parent reply	other threads:[~2018-03-02 16:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-19 14:51 [PATCH 0/4] cleanups and new HW rev support Gilad Ben-Yossef
2018-02-19 14:51 ` [PATCH 1/4] crypto: ccree: remove unused definitions Gilad Ben-Yossef
2018-02-19 14:51 ` [PATCH 2/4] dt-bindings: Add DT bindings for ccree 710 and 630p Gilad Ben-Yossef
2018-02-19 20:49   ` Rob Herring
2018-02-19 14:51 ` [PATCH 3/4] crypto: ccree: add support for older HW revs Gilad Ben-Yossef
2018-02-19 14:51 ` [PATCH 4/4] crypto: ccree: replace memset+kfree with kzfree Gilad Ben-Yossef
2018-03-02 16:42 ` Herbert Xu [this message]

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=20180302164212.GE21579@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=gilad@benyossef.com \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=ofir.drang@arm.com \
    --cc=robh+dt@kernel.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).