From: Akhil Goyal <akhil.goyal@nxp.com>
To: "asomalap@amd.com" <asomalap@amd.com>,
"dev@dpdk.org" <dev@dpdk.org>,
"Kumar, Ravi1" <Ravi1.Kumar@amd.com>
Cc: "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2] crypto/ccp: enable IOMMU for CCP
Date: Wed, 12 Feb 2020 07:11:15 +0000 [thread overview]
Message-ID: <DB8PR04MB6635FB5262F417F48088CDC0E61B0@DB8PR04MB6635.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20200128083819.32834-1-asomalap@amd.com>
>
> CCP use vdev framework, and vdev framework don’t support IOMMU.
> Adding custom IOMMU support for AMD CCP drives.
> Cc: stable@dpdk.org
>
> Signed-off-by: Amaranath Somalapuram <asomalap@amd.com>
> ---
Is it a fix or a new feature?
If it is a fix then only it should be sent to stable and the patch title should include "crypto/ccp: fix ...".
If it is a feature(which is more likely the case IMO), the title is fine or I would change it to "crypto/ccp: enable IOMMU"
@Ravi: could you please review this patch.
next prev parent reply other threads:[~2020-02-12 7:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 8:38 asomalap
2020-02-12 7:11 ` Akhil Goyal [this message]
2020-02-12 7:44 ` Somalapuram, Amaranath
2020-02-12 10:05 ` Akhil Goyal
2020-02-12 10:31 ` Kumar, Ravi1
2020-02-12 13:50 ` Akhil Goyal
2020-02-14 15:53 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2020-12-25 8:03 ` [dpdk-dev] [PATCH v3] " asomalap
2021-01-15 15:58 ` Akhil Goyal
2021-05-27 13:24 ` David Marchand
2021-05-27 14:10 ` Thomas Monjalon
2021-05-28 5:02 ` Somalapuram, Amaranath
2021-05-28 7:20 ` Thomas Monjalon
2021-05-28 9:40 ` Somalapuram, Amaranath
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=DB8PR04MB6635FB5262F417F48088CDC0E61B0@DB8PR04MB6635.eurprd04.prod.outlook.com \
--to=akhil.goyal@nxp.com \
--cc=Ravi1.Kumar@amd.com \
--cc=asomalap@amd.com \
--cc=dev@dpdk.org \
--cc=stable@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).