DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
To: "Sebastian, Selwin" <Selwin.Sebastian@amd.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Sebastian, Selwin" <Selwin.Sebastian@amd.com>
Subject: Re: [dpdk-dev] [PATCH v1] crypto/ccp: add support for new CCP device ID
Date: Tue, 21 Jan 2020 06:06:11 +0000	[thread overview]
Message-ID: <MW2PR12MB257008A078C757D23EF9D3EBAE0D0@MW2PR12MB2570.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20191230163449.16342-1-Selwin.Sebastian@amd.com>

[AMD Public Use]


Looks good to me. 

Acked-by: Ravi Kumar <ravi1.kumar@amd.com>

Regards,
Ravi

>-----Original Message-----
>From: dev <dev-bounces@dpdk.org> On Behalf Of Selwin Sebastian
>Sent: Monday, December 30, 2019 10:05 PM
>To: dev@dpdk.org
>Cc: Sebastian, Selwin <Selwin.Sebastian@amd.com>
>Subject: [dpdk-dev] [PATCH v1] crypto/ccp: add support for new CCP device ID
>
>[CAUTION: External Email]
>
>Add a new CCP PCI device ID for supporting V1000/R1000 processors.
>
>Signed-off-by: Selwin Sebastian <Selwin.Sebastian@amd.com>
>---
> drivers/crypto/ccp/rte_ccp_pmd.c | 3 +++
> 1 file changed, 3 insertions(+)
>
>diff --git a/drivers/crypto/ccp/rte_ccp_pmd.c b/drivers/crypto/ccp/rte_ccp_pmd.c
>index 38cb1fe3d..b5bb6790b 100644
>--- a/drivers/crypto/ccp/rte_ccp_pmd.c
>+++ b/drivers/crypto/ccp/rte_ccp_pmd.c
>@@ -292,6 +292,9 @@ static struct rte_pci_id ccp_pci_id[] = {
>        {
>                RTE_PCI_DEVICE(0x1022, 0x1468), /* AMD CCP-5b */
>        },
>+       {
>+               RTE_PCI_DEVICE(0x1022, 0x15df), /* AMD CCP RV */
>+       },
>        {.device_id = 0},
> };
>
>--
>2.17.1
>
>

  reply	other threads:[~2020-01-21  6:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-30 16:34 Selwin Sebastian
2020-01-21  6:06 ` Kumar, Ravi1 [this message]
2020-01-28  6:11   ` 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=MW2PR12MB257008A078C757D23EF9D3EBAE0D0@MW2PR12MB2570.namprd12.prod.outlook.com \
    --to=ravi1.kumar@amd.com \
    --cc=Selwin.Sebastian@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).