linux-crypto.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Herbert Xu <herbert@gondor.apana.org.au>
To: Rob Rice <rob.rice@broadcom.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	linux-crypto@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/3] Add Broadcom SPU Crypto Driver
Date: Sat, 11 Feb 2017 18:54:04 +0800	[thread overview]
Message-ID: <20170211105404.GF855@gondor.apana.org.au> (raw)
In-Reply-To: <1486144534-44887-1-git-send-email-rob.rice@broadcom.com>

On Fri, Feb 03, 2017 at 12:55:31PM -0500, Rob Rice wrote:
> Changes in v4:
> - Added Rob Herring's Acked-by to patch 1/3 for bindings doc
> - In response to Herbert's comment, in ahash_export() and 
>   ahash_import(), only copy the hash state, not state params
>   related to cipher or aead algos. 
> - Noticed that hmac_offset in iproc_reqctx_s and spu_hash_params
>   wasn't really used. So removed.

Patches 1-2 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:[~2017-02-11 10:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 17:55 Rob Rice
2017-02-03 17:55 ` [PATCH v4 1/3] crypto: brcm: DT documentation for Broadcom SPU hardware Rob Rice
2017-02-03 17:55 ` [PATCH v4 2/3] crypto: brcm: Add Broadcom SPU driver Rob Rice
2017-02-03 17:55 ` [PATCH v4 3/3] arm64: dts: ns2: Add Broadcom SPU driver DT entry Rob Rice
2017-02-11 10:54 ` Herbert Xu [this message]
2017-02-13 15:11   ` [PATCH v4 0/3] Add Broadcom SPU Crypto Driver Jon Mason
2017-02-28 20:14     ` Florian Fainelli

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=20170211105404.GF855@gondor.apana.org.au \
    --to=herbert@gondor.apana.org.au \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=catalin.marinas@arm.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-crypto@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rob.rice@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=will.deacon@arm.com \
    --subject='Re: [PATCH v4 0/3] Add Broadcom SPU Crypto Driver' \
    /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

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).