DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bernard Iremonger <bernard.iremonger@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH v4 14/20] fm10k: copy pci device info to eth_dev data
Date: Wed, 21 Oct 2015 15:50:38 +0100	[thread overview]
Message-ID: <1445439044-2987-15-git-send-email-bernard.iremonger@intel.com> (raw)
In-Reply-To: <1445439044-2987-1-git-send-email-bernard.iremonger@intel.com>

Signed-off-by: Bernard Iremonger <bernard.iremonger@intel.com>
---
 drivers/net/fm10k/fm10k_ethdev.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/drivers/net/fm10k/fm10k_ethdev.c b/drivers/net/fm10k/fm10k_ethdev.c
index a69c990..12be227 100644
--- a/drivers/net/fm10k/fm10k_ethdev.c
+++ b/drivers/net/fm10k/fm10k_ethdev.c
@@ -2075,6 +2075,8 @@ eth_fm10k_dev_init(struct rte_eth_dev *dev)
 	if (rte_eal_process_type() != RTE_PROC_PRIMARY)
 		return 0;
 
+	rte_eth_copy_dev_info(dev, dev->pci_dev);
+
 	macvlan = FM10K_DEV_PRIVATE_TO_MACVLAN(dev->data->dev_private);
 	memset(macvlan, 0, sizeof(*macvlan));
 	/* Vendor and Device ID need to be set before init of shared code */
-- 
1.9.1

  parent reply	other threads:[~2015-10-21 14:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <PATCH v4>
2015-10-21 14:50 ` [dpdk-dev] [PATCH v4 00/20] remove pci driver from vdevs Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 01/20] librte_eal: add RTE_KDRV_NONE for vdevs Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 02/20] librte_ether: add fields from rte_pci_driver to rte_eth_dev_data Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 03/20] librte_ether: add function rte_eth_copy_dev_info() Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 04/20] null: remove pci device driver Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 05/20] ring: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 06/20] bonding: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 07/20] pcap: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 08/20] af_packet: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 09/20] xenvirt: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 10/20] mpipe: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 11/20] ixgbe: copy pci device info to eth_dev data Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 12/20] e1000: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 13/20] i40e: " Bernard Iremonger
2015-10-21 14:50   ` Bernard Iremonger [this message]
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 15/20] bnx2x: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 16/20] cxgbe: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 17/20] enic: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 18/20] mlx4: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 19/20] virtio: " Bernard Iremonger
2015-10-21 14:50   ` [dpdk-dev] [PATCH v4 20/20] vmxnet3: " Bernard Iremonger

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=1445439044-2987-15-git-send-email-bernard.iremonger@intel.com \
    --to=bernard.iremonger@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).