From: Sasha Levin <levinsasha928@gmail.com>
To: George Cherian <george.cherian@cavium.com>, alexander.levin@verizon.com
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
davem <davem@davemloft.net>,
david.daney@cavium.com,
corentin labbe <clabbe.montjoie@gmail.com>,
smueller@chronox.de,
"linux-kernel@vger.kernel.org List"
<linux-kernel@vger.kernel.org>,
linux-crypto@vger.kernel.org
Subject: Re: [PATCH v5 0/3] Add Support for Cavium Cryptographic Acceleration Unit
Date: Fri, 3 Feb 2017 12:32:12 -0500 [thread overview]
Message-ID: <CA+1xoqcWSdKtqvEQaGU+RQmxY3ZsH6L9G8_yFUODGcDksLuTiw@mail.gmail.com> (raw)
In-Reply-To: <1485779444-4332-1-git-send-email-george.cherian@cavium.com>
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian
<george.cherian@cavium.com> 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.
Can we have the firmware now to be able to actually test this series?
next prev parent reply other threads:[~2017-02-03 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 12:30 [PATCH v5 0/3] Add Support for Cavium Cryptographic Acceleration Unit George Cherian
2017-01-30 12:30 ` [PATCH v5 1/3] drivers: crypto: Add Support for Octeon-tx CPT Engine George Cherian
2017-01-30 12:30 ` [PATCH v5 2/3] drivers: crypto: Add the Virtual Function driver for CPT George Cherian
2017-02-02 18:54 ` Sasha Levin
2017-02-04 4:37 ` George Cherian
2017-01-30 12:30 ` [PATCH v5 3/3] drivers: crypto: Enable CPT options crypto for build George Cherian
2017-02-03 17:32 ` Sasha Levin [this message]
2017-02-04 5:17 ` [PATCH v5 0/3] Add Support for Cavium Cryptographic Acceleration Unit George Cherian
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=CA+1xoqcWSdKtqvEQaGU+RQmxY3ZsH6L9G8_yFUODGcDksLuTiw@mail.gmail.com \
--to=levinsasha928@gmail.com \
--cc=alexander.levin@verizon.com \
--cc=clabbe.montjoie@gmail.com \
--cc=davem@davemloft.net \
--cc=david.daney@cavium.com \
--cc=george.cherian@cavium.com \
--cc=herbert@gondor.apana.org.au \
--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;
as well as URLs for NNTP newsgroup(s).