From: Stephen Hemminger <stephen@networkplumber.org>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: Add support for new PCI IDs
Date: Mon, 9 Jan 2017 09:03:28 -0800 [thread overview]
Message-ID: <20170109090328.4768b23f@xeon-e3> (raw)
In-Reply-To: <20170106195517.52821-1-ajit.khaparde@broadcom.com>
fine BROADCOM_DEV_ID_57416_MF 0x16ee
>
> static struct rte_pci_id bnxt_pci_id_map[] = {
> { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57301) },
> @@ -95,6 +110,21 @@ static struct rte_pci_id bnxt_pci_id_map[] = {
> { RTE_PCI_DEVICE(PCI_VENDOR_ID_BROADCOM, BROADCOM_DEV_ID_57407_MF) },
Adding new id's is good. Does this now cover all the devices in the Linux kernel?
The PCI id table should be const?
prev parent reply other threads:[~2017-01-09 17:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-06 19:55 Ajit Khaparde
2017-01-09 11:55 ` Ferruh Yigit
2017-01-09 17:03 ` Stephen Hemminger [this message]
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=20170109090328.4768b23f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=ajit.khaparde@broadcom.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).