From: "Zhang, Helin" <helin.zhang@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] nic_uio: add device ids for i40e devices
Date: Fri, 11 Jul 2014 02:58:18 +0000 [thread overview]
Message-ID: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A74C061@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <59AF69C657FD0841A61C55336867B5B0343AC9C0@IRSMSX103.ger.corp.intel.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Richardson, Bruce
> Sent: Friday, July 11, 2014 8:13 AM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH] nic_uio: add device ids for i40e devices
>
> The FreeBSD nic_uio driver was missing the #defines to include the device ids
> for devices using the i40e driver. This change adds in the missing defines.
>
> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
> ---
> lib/librte_eal/bsdapp/nic_uio/nic_uio.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
> b/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
> index 3fe6f1c..8ba7f1b 100644
> --- a/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
> +++ b/lib/librte_eal/bsdapp/nic_uio/nic_uio.c
> @@ -109,6 +109,8 @@ struct pci_bdf {
> #define RTE_PCI_DEV_ID_DECL_IGBVF(vend, dev) {vend, dev},
> #define RTE_PCI_DEV_ID_DECL_IXGBE(vend, dev) {vend, dev},
> #define RTE_PCI_DEV_ID_DECL_IXGBEVF(vend, dev) {vend, dev},
> +#define RTE_PCI_DEV_ID_DECL_I40E(vend, dev) {vend, dev},
> +#define RTE_PCI_DEV_ID_DECL_I40EVF(vend, dev) {vend, dev},
> #define RTE_PCI_DEV_ID_DECL_VIRTIO(vend, dev) {vend, dev},
>
> const struct device devices[] = {
> --
> 2.0.0
Acked-by: Helin Zhang <helin.zhang@intel.com>
next prev parent reply other threads:[~2014-07-11 2:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1405004940-6592-1-git-send-email-bruce.richardson@intel.com>
2014-07-11 0:12 ` Richardson, Bruce
2014-07-11 2:58 ` Zhang, Helin [this message]
2014-07-18 23:49 ` Thomas Monjalon
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=F35DEAC7BCE34641BA9FAC6BCA4A12E70A74C061@SHSMSX104.ccr.corp.intel.com \
--to=helin.zhang@intel.com \
--cc=bruce.richardson@intel.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).