From: Akhil Goyal <gakhil@marvell.com>
To: "asomalap@amd.com" <asomalap@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [EXT] [PATCH v6] crypto/ccp: move device from vdev to PCI
Date: Tue, 27 Jul 2021 17:39:06 +0000 [thread overview]
Message-ID: <PH0PR18MB44914B9C8C9316B5041414DBD8E99@PH0PR18MB4491.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20210726090821.3833862-1-asomalap@amd.com>
> From: Amaranath Somalapuram <Amaranath.Somalapuram@amd.com>
>
> drop all the code duplicating the PCI bus driver
> developed for enable IOMMU in vdev.
>
> Signed-off-by: Amaranath Somalapuram
> <Amaranath.Somalapuram@amd.com>
> ---
> V6:
> - Address the following comments from Akhil and David:
> - Spellcheck, Title, Changelog
>
Applied to dpdk-next-crypto
next prev parent reply other threads:[~2021-07-27 17:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 12:02 [dpdk-dev] [PATCH v4] crypto/ccp: moving vdev to PCI driver asomalap
2021-07-16 12:11 ` David Marchand
2021-07-19 4:46 ` [dpdk-dev] [PATCH v5] " asomalap
2021-07-19 18:55 ` [dpdk-dev] [EXT] " Akhil Goyal
2021-07-26 9:08 ` [dpdk-dev] [PATCH v6] crypto/ccp: move device from vdev to PCI asomalap
2021-07-27 17:39 ` Akhil Goyal [this message]
2023-10-06 11:06 ` David Marchand
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=PH0PR18MB44914B9C8C9316B5041414DBD8E99@PH0PR18MB4491.namprd18.prod.outlook.com \
--to=gakhil@marvell.com \
--cc=asomalap@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).