From: meenakshi.aggarwal@nxp.com
To: Horia Geanta <horia.geanta@nxp.com>,
Pankaj Gupta <pankaj.gupta@nxp.com>,
Gaurav Jain <gaurav.jain@nxp.com>, Varun Sethi <V.Sethi@nxp.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-imx@nxp.com,
Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
Subject: [PATCH v5 0/1] crypto: caam/rng: Add support for PRNG
Date: Fri, 29 Apr 2022 13:48:07 +0200 [thread overview]
Message-ID: <20220429114808.147108-1-meenakshi.aggarwal@nxp.com> (raw)
In-Reply-To: <20220429084527.2069402-1-meenakshi.aggarwal@nxp.com>
From: Meenakshi Aggarwal <meenakshi.aggarwal@nxp.com>
changes in v5:
- incorporated review comments
Meenakshi Aggarwal (1):
crypto: caam/rng: Add support for PRNG
drivers/crypto/caam/Kconfig | 8 ++
drivers/crypto/caam/Makefile | 1 +
drivers/crypto/caam/caamprng.c | 235 +++++++++++++++++++++++++++++++++
drivers/crypto/caam/intern.h | 15 +++
drivers/crypto/caam/jr.c | 3 +-
5 files changed, 261 insertions(+), 1 deletion(-)
create mode 100644 drivers/crypto/caam/caamprng.c
base-commit: 38d741cb70b30741c0e802cbed7bd9cf4fd15fa4
--
2.25.1
next prev parent reply other threads:[~2022-04-29 11:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-04 11:41 [PATCH] crypto: caam/rng: Add support for PRNG meenakshi.aggarwal
2022-03-08 22:49 ` kernel test robot
2022-03-16 18:01 ` [PATCH v2 0/1] " meenakshi.aggarwal
2022-03-16 18:01 ` [PATCH v2 1/1] " meenakshi.aggarwal
2022-04-05 12:31 ` Horia Geantă
2022-04-20 5:57 ` Meenakshi Aggarwal
2022-04-20 6:38 ` [PATCH v3 0/1] " meenakshi.aggarwal
2022-04-20 6:38 ` [PATCH v3 1/1] " meenakshi.aggarwal
2022-04-27 11:48 ` Horia Geantă
2022-04-29 8:45 ` [PATCH v4 0/1] " meenakshi.aggarwal
2022-04-29 8:45 ` [PATCH v4 1/1] " meenakshi.aggarwal
2022-04-29 11:01 ` Horia Geantă
2022-04-29 11:48 ` meenakshi.aggarwal [this message]
2022-04-29 11:48 ` [PATCH v5 " meenakshi.aggarwal
2022-05-06 10:22 ` Herbert Xu
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=20220429114808.147108-1-meenakshi.aggarwal@nxp.com \
--to=meenakshi.aggarwal@nxp.com \
--cc=V.Sethi@nxp.com \
--cc=davem@davemloft.net \
--cc=gaurav.jain@nxp.com \
--cc=herbert@gondor.apana.org.au \
--cc=horia.geanta@nxp.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pankaj.gupta@nxp.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.