From: "Uttarwar, Sunil Prakashrao" <SunilPrakashrao.Uttarwar@amd.com>
To: David Marchand <david.marchand@redhat.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>
Subject: RE: [PATCH v2 0/4] crypto/ccp cleanup
Date: Tue, 11 Oct 2022 11:44:07 +0000 [thread overview]
Message-ID: <CY4PR1201MB019973F6F0EDEF9193A1946292239@CY4PR1201MB0199.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221004095132.198777-1-david.marchand@redhat.com>
[Public]
-----Original Message-----
From: David Marchand <david.marchand@redhat.com>
Sent: Tuesday, October 4, 2022 3:21 PM
To: dev@dpdk.org
Cc: gakhil@marvell.com; Uttarwar, Sunil Prakashrao <SunilPrakashrao.Uttarwar@amd.com>
Subject: [PATCH v2 0/4] crypto/ccp cleanup
For this series
Below shared patches seems fine, verified on AMD platform works fine.
crypto/ccp: fix IOVA handling
crypto/ccp: remove some dead code for UIO
crypto/ccp: remove some printf
Now working on the "crypto/ccp: fix PCI probing" patch and will update on this.
Thanks
Sunil
next prev parent reply other threads:[~2022-10-11 11:44 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 15:04 [PATCH " David Marchand
2022-09-09 15:04 ` [PATCH 1/4] crypto/ccp: remove some printf David Marchand
2022-09-09 15:04 ` [PATCH 2/4] crypto/ccp: remove some dead code for UIO David Marchand
2022-09-09 15:04 ` [PATCH 3/4] crypto/ccp: fix IOVA handling David Marchand
2022-09-09 15:04 ` [PATCH 4/4] crypto/ccp: fix PCI probing David Marchand
2022-10-04 9:51 ` [PATCH v2 0/4] crypto/ccp cleanup David Marchand
2022-10-04 9:51 ` [PATCH v2 1/4] crypto/ccp: remove some printf David Marchand
2023-01-13 11:58 ` Uttarwar, Sunil Prakashrao
2023-01-30 18:42 ` [EXT] " Akhil Goyal
2022-10-04 9:51 ` [PATCH v2 2/4] crypto/ccp: remove some dead code for UIO David Marchand
2023-01-13 12:00 ` Uttarwar, Sunil Prakashrao
2022-10-04 9:51 ` [PATCH v2 3/4] crypto/ccp: fix IOVA handling David Marchand
2023-01-13 12:00 ` Uttarwar, Sunil Prakashrao
2022-10-04 9:51 ` [PATCH v2 4/4] crypto/ccp: fix PCI probing David Marchand
2022-10-07 6:54 ` [EXT] [PATCH v2 0/4] crypto/ccp cleanup Akhil Goyal
2022-10-11 11:44 ` Uttarwar, Sunil Prakashrao [this message]
2022-10-13 9:40 ` Akhil Goyal
2022-10-17 13:42 ` Uttarwar, Sunil Prakashrao
2022-10-17 13:53 ` David Marchand
2022-10-26 6:21 ` David Marchand
[not found] ` <1ec3f0fc-631f-2aa6-70f7-7f9b96caa2a2@amd.com>
[not found] ` <CY4PR1201MB019989039CF117EE75F9025692399@CY4PR1201MB0199.namprd12.prod.outlook.com>
[not found] ` <CAJFAV8xpZM96qDzaezO64LsRSdhWu8A2quCo8xGpufRrfjrMSw@mail.gmail.com>
[not found] ` <CY4PR1201MB01992328892E48006952D3C892399@CY4PR1201MB0199.namprd12.prod.outlook.com>
2022-11-03 13:08 ` David Marchand
2022-11-18 11:58 ` Uttarwar, Sunil Prakashrao
2023-01-11 15:14 ` David Marchand
2023-01-12 12:28 ` Uttarwar, Sunil Prakashrao
2023-01-17 13:56 ` Uttarwar, Sunil Prakashrao
2023-03-02 11:43 ` [PATCH v2] crypto/ccp: fix PCI probing David Marchand
2023-03-06 12:05 ` Uttarwar, Sunil Prakashrao
2023-03-11 18:49 ` 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=CY4PR1201MB019973F6F0EDEF9193A1946292239@CY4PR1201MB0199.namprd12.prod.outlook.com \
--to=sunilprakashrao.uttarwar@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.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).