From: Herbert Xu <herbert@gondor.apana.org.au>
To: George Cherian <george.cherian@cavium.com>
Cc: davem@davemloft.net, david.daney@cavium.com,
clabbe.montjoie@gmail.com, smueller@chronox.de,
levinsasha928@gmail.com, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v6 0/3] Add Support for Cavium Cryptographic Acceleration Unit
Date: Sat, 11 Feb 2017 18:57:07 +0800 [thread overview]
Message-ID: <20170211105707.GL855@gondor.apana.org.au> (raw)
In-Reply-To: <1486479075-1813-1-git-send-email-george.cherian@cavium.com>
On Tue, Feb 07, 2017 at 02:51:12PM +0000, George Cherian wrote:
> This series adds the support for Cavium Cryptographic Accelerarion Unit (CPT)
> CPT is available in Cavium's Octeon-Tx SoC series.
>
> The series was tested with ecryptfs and dm-crypt for in kernel cryptographic
> offload operations. This driver needs a firmware to work, I will be sending the
> firmware to linux-firmware once the driver is accepted.
>
> Cahnges v5 -> v6
> -- Addressed Sasha Levin's comments.
> - Remove open coding of hlist_for_each_entry_safe, instead use
> the same.
> - Remove the direct access of hlist members
> - Remove unwanted argument checks.
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-02-11 18:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 14:51 [PATCH v6 0/3] Add Support for Cavium Cryptographic Acceleration Unit George Cherian
2017-02-07 14:51 ` [PATCH v6 1/3] drivers: crypto: Add Support for Octeon-tx CPT Engine George Cherian
2017-02-07 14:51 ` [PATCH v6 2/3] drivers: crypto: Add the Virtual Function driver for CPT George Cherian
2017-02-07 14:51 ` [PATCH v6 3/3] drivers: crypto: Enable CPT options crypto for build George Cherian
2017-02-11 10:57 ` 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=20170211105707.GL855@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=george.cherian@cavium.com \
--cc=levinsasha928@gmail.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smueller@chronox.de \
/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