From: Herbert Xu <herbert@gondor.apana.org.au>
To: Gary R Hook <gary.hook@amd.com>
Cc: linux-crypto@vger.kernel.org, thomas.lendacky@amd.com,
davem@davemloft.net
Subject: Re: [PATCH v3 0/3] Update support for XTS-AES on AMD CCPs
Date: Thu, 3 Aug 2017 14:27:31 +0800 [thread overview]
Message-ID: <20170803062731.GT12039@gondor.apana.org.au> (raw)
In-Reply-To: <150100997531.39154.470521200404215266.stgit@sosxen.amd.com>
On Tue, Jul 25, 2017 at 02:21:12PM -0500, Gary R Hook wrote:
> The following series adds support for XS-AES on version 5 CCPs, both
> 128- and 256-bit, and enhances/clarifies/simplifies some crypto layer
> code.
>
> Changes since v2:
> - Move a CCP v5 fix out of this patch series and submit independently
> - In the unit-size check patch:
> - Edit comments
> - Remove unnecessary variable
> - Delay a change (that belongs in the CCP v5 patch)
>
> Changes since v1:
> - rework the validation of the unit-size; move to a separate patch
> - expand the key buffer to accommodate 256-bit keys
> - use xts_check_key() in the crypto layer
>
>
> ---
>
> Gary R Hook (3):
> crypto: ccp - Add a call to xts_check_key()
> crypto: ccp - Rework the unit-size check for XTS-AES
> crypto: ccp - Add XTS-AES-256 support for CCP version 5
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
prev parent reply other threads:[~2017-08-03 6:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 19:21 [PATCH v3 0/3] Update support for XTS-AES on AMD CCPs Gary R Hook
2017-07-25 19:21 ` [PATCH v3 1/3] crypto: ccp - Add a call to xts_check_key() Gary R Hook
2017-07-25 19:21 ` [PATCH v3 2/3] crypto: ccp - Rework the unit-size check for XTS-AES Gary R Hook
2017-07-25 19:21 ` [PATCH v3 3/3] crypto: ccp - Add XTS-AES-256 support for CCP version 5 Gary R Hook
2017-07-25 22:43 ` [PATCH v3 0/3] Update support for XTS-AES on AMD CCPs Gary R Hook
2017-08-03 6:27 ` 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=20170803062731.GT12039@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=davem@davemloft.net \
--cc=gary.hook@amd.com \
--cc=linux-crypto@vger.kernel.org \
--cc=thomas.lendacky@amd.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.