From: Herbert Xu <herbert@gondor.apana.org.au>
To: Srikanth Jampala <Jampala.Srikanth@cavium.com>
Cc: davem@davemloft.net, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org, sgadam@cavium.com
Subject: Re: [PATCH cryptodev-2.6 1/3] crypto: cavium/nitrox - added support to identify the NITROX device partname.
Date: Fri, 28 Sep 2018 13:09:48 +0800 [thread overview]
Message-ID: <20180928050948.qmoul4drqhs3n7cz@gondor.apana.org.au> (raw)
In-Reply-To: <20180921113802.26475-1-Jampala.Srikanth@cavium.com>
On Fri, Sep 21, 2018 at 05:08:00PM +0530, Srikanth Jampala wrote:
> Get the device partname based on it's capabilities like,
> core frequency, number of cores and revision id.
>
> Signed-off-by: Srikanth Jampala <Jampala.Srikanth@cavium.com>
> ---
> drivers/crypto/cavium/nitrox/nitrox_csr.h | 111 +++++++++++++++++++++
> drivers/crypto/cavium/nitrox/nitrox_dev.h | 17 +++-
> drivers/crypto/cavium/nitrox/nitrox_hal.c | 57 +++++++++++
> drivers/crypto/cavium/nitrox/nitrox_hal.h | 1 +
> drivers/crypto/cavium/nitrox/nitrox_main.c | 20 ----
> 5 files changed, 184 insertions(+), 22 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
prev parent reply other threads:[~2018-09-28 5:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 11:38 [PATCH cryptodev-2.6 1/3] crypto: cavium/nitrox - added support to identify the NITROX device partname Srikanth Jampala
2018-09-21 11:38 ` [PATCH cryptodev-2.6 2/3] crypto: cavium/nitrox - add support for per device request statistics Srikanth Jampala
2018-09-21 11:38 ` [PATCH cryptodev-2.6 3/3] crypto: cavium/nitrox - updated debugfs information Srikanth Jampala
2018-09-28 13:31 ` Ard Biesheuvel
2018-09-28 14:41 ` Srikanth, Jampala
2018-09-28 5:09 ` 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=20180928050948.qmoul4drqhs3n7cz@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=Jampala.Srikanth@cavium.com \
--cc=davem@davemloft.net \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sgadam@cavium.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 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).