From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ye Xiaolong <xiaolong.ye@intel.com>, Ting Xu <ting.xu@intel.com>
Cc: dev@dpdk.org, wenzhuo.lu@intel.com, qiming.yang@intel.com,
qi.z.zhang@intel.com
Subject: Re: [dpdk-dev] [PATCH v1] net/ice: add new device IDs
Date: Thu, 19 Dec 2019 12:13:45 +0000 [thread overview]
Message-ID: <dec2412e-d5c3-9011-ecc5-f755ccdb8390@intel.com> (raw)
In-Reply-To: <20191219024346.GU59123@intel.com>
On 12/19/2019 2:43 AM, Ye Xiaolong wrote:
> On 12/18, Ting Xu wrote:
>> This patch added new device IDs for C822N.
>>
>> Signed-off-by: Ting Xu <ting.xu@intel.com>
>> ---
>> drivers/net/ice/ice_ethdev.c | 3 +++
>> 1 file changed, 3 insertions(+)
>>
>> diff --git a/drivers/net/ice/ice_ethdev.c b/drivers/net/ice/ice_ethdev.c
>> index de189daba..2cbd82c94 100644
>> --- a/drivers/net/ice/ice_ethdev.c
>> +++ b/drivers/net/ice/ice_ethdev.c
>> @@ -163,6 +163,9 @@ static const struct rte_pci_id pci_id_ice_map[] = {
>> { RTE_PCI_DEVICE(ICE_INTEL_VENDOR_ID, ICE_DEV_ID_E810_XXV_BACKPLANE) },
>> { RTE_PCI_DEVICE(ICE_INTEL_VENDOR_ID, ICE_DEV_ID_E810_XXV_QSFP) },
>> { RTE_PCI_DEVICE(ICE_INTEL_VENDOR_ID, ICE_DEV_ID_E810_XXV_SFP) },
>> + { RTE_PCI_DEVICE(ICE_INTEL_VENDOR_ID, ICE_DEV_ID_C822N_BACKPLANE) },
>> + { RTE_PCI_DEVICE(ICE_INTEL_VENDOR_ID, ICE_DEV_ID_C822N_QSFP) },
>> + { RTE_PCI_DEVICE(ICE_INTEL_VENDOR_ID, ICE_DEV_ID_C822N_SFP) },
>> { .vendor_id = 0, /* sentinel */ },
>> };
>>
>> --
>> 2.17.1
>>
>
> Acked-by: Xiaolong Ye <xiaolong.ye@intel.com>
>
> Applied to dpdk-next-net-intel, Thanks.
>
Just to double check, if this requires any update in the NIC documentation?
next prev parent reply other threads:[~2019-12-19 12:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 12:41 Ting Xu
2019-12-19 2:43 ` Ye Xiaolong
2019-12-19 12:13 ` Ferruh Yigit [this message]
2019-12-20 7:01 ` Xu, Ting
2019-12-20 8:54 ` Ferruh Yigit
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=dec2412e-d5c3-9011-ecc5-f755ccdb8390@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=ting.xu@intel.com \
--cc=wenzhuo.lu@intel.com \
--cc=xiaolong.ye@intel.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).