From: Akhil Goyal <gakhil@marvell.com>
To: Andrew Boyer <andrew.boyer@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH v2 3/9] crypto/ionic: add device commands
Date: Sat, 1 Jun 2024 13:57:44 +0000 [thread overview]
Message-ID: <CO6PR18MB44849F18622665D76777EF4BD8FD2@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20240430202144.49899-4-andrew.boyer@amd.com>
> Subject: [EXTERNAL] [PATCH v2 3/9] crypto/ionic: add device commands
>
> This defines the device (register-based) commands. They are used for
> device identification, setup, and teardown.
>
> Signed-off-by: Andrew Boyer <andrew.boyer@amd.com>
> ---
> drivers/crypto/ionic/ionic_crypto.h | 24 ++
> drivers/crypto/ionic/ionic_crypto_cmds.c | 348 +++++++++++++++++++++++
> drivers/crypto/ionic/ionic_crypto_main.c | 89 +++++-
> drivers/crypto/ionic/meson.build | 1 +
> 4 files changed, 461 insertions(+), 1 deletion(-)
> create mode 100644 drivers/crypto/ionic/ionic_crypto_cmds.c
>
Fix _coding style issues_
Warning in drivers/crypto/ionic/ionic_crypto_cmds.c:
Using %l format, prefer %PRI*64 if type is [u]int64_t
next prev parent reply other threads:[~2024-06-01 13:57 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 19:53 [PATCH 0/6] crypto/ionic: introduce AMD Pensando ionic crypto driver Andrew Boyer
2024-04-19 19:53 ` [PATCH 1/6] " Andrew Boyer
2024-04-19 19:53 ` [PATCH 2/6] crypto/ionic: add device and admin command handlers Andrew Boyer
2024-04-22 12:29 ` Boyer, Andrew
2024-04-19 19:53 ` [PATCH 3/6] common/ionic: add crypto vdev support Andrew Boyer
2024-04-19 19:53 ` [PATCH 4/6] crypto/ionic: add device object and " Andrew Boyer
2024-04-19 19:53 ` [PATCH 5/6] crypto/ionic: add datapath and capabilities support Andrew Boyer
2024-04-19 19:53 ` [PATCH 6/6] crypto/ionic: add documentation and connect to build Andrew Boyer
2024-04-24 18:21 ` [EXTERNAL] [PATCH 0/6] crypto/ionic: introduce AMD Pensando ionic crypto driver Akhil Goyal
2024-04-30 20:21 ` [PATCH v2 0/9] " Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 1/9] " Andrew Boyer
2024-05-30 12:02 ` [EXTERNAL] " Akhil Goyal
2024-06-05 1:27 ` Boyer, Andrew
2024-06-06 10:47 ` Akhil Goyal
2024-06-07 14:27 ` [PATCH v3 0/9] crypto/ionic: introduce AMD Pensando driver Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 1/9] " Andrew Boyer
2024-06-13 10:07 ` [EXTERNAL] " Akhil Goyal
2024-06-13 14:45 ` Boyer, Andrew
2024-06-13 17:58 ` Akhil Goyal
2024-06-07 14:27 ` [PATCH v3 2/9] crypto/ionic: add the firmware interface definition file Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 3/9] crypto/ionic: add device commands Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 4/9] crypto/ionic: add adminq command support Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 5/9] crypto/ionic: add capabilities and basic ops Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 6/9] crypto/ionic: add session support Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 7/9] crypto/ionic: add datapath Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 8/9] crypto/ionic: add a watchdog operation Andrew Boyer
2024-06-07 14:27 ` [PATCH v3 9/9] crypto/ionic: add stats support Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 2/9] crypto/ionic: add the firmware interface definition file Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 3/9] crypto/ionic: add device commands Andrew Boyer
2024-06-01 13:57 ` Akhil Goyal [this message]
2024-06-05 1:23 ` [EXTERNAL] " Boyer, Andrew
2024-04-30 20:21 ` [PATCH v2 4/9] crypto/ionic: add adminq command support Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 5/9] crypto/ionic: add capabilities and basic ops Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 6/9] crypto/ionic: add session support Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 7/9] crypto/ionic: add datapath Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 8/9] crypto/ionic: add a watchdog operation Andrew Boyer
2024-04-30 20:21 ` [PATCH v2 9/9] crypto/ionic: add stats support Andrew Boyer
2024-06-04 13:28 ` [PATCH v2 0/9] crypto/ionic: introduce AMD Pensando ionic crypto driver Boyer, Andrew
2024-06-04 14:49 ` Boyer, Andrew
2024-06-06 10:57 ` Akhil Goyal
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=CO6PR18MB44849F18622665D76777EF4BD8FD2@CO6PR18MB4484.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=andrew.boyer@amd.com \
--cc=dev@dpdk.org \
/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).