DPDK patches and discussions
 help / color / mirror / Atom feed
From: Olivier Matz <olivier.matz@6wind.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 01/10] bsd/pci: rename device and driver lists
Date: Fri, 25 Apr 2014 13:59:39 +0200	[thread overview]
Message-ID: <1398427188-14914-2-git-send-email-olivier.matz@6wind.com> (raw)
In-Reply-To: <1398427188-14914-1-git-send-email-olivier.matz@6wind.com>

The bsdapp part was missing in commit 5b1f4a67dd5bcfa8d5139c064ced6e37a9149419.

To avoid confusion with virtual devices, rename device_list as
pci_device_list and driver_list as pci_driver_list.

Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
---
 lib/librte_eal/bsdapp/eal/eal_pci.c | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/lib/librte_eal/bsdapp/eal/eal_pci.c b/lib/librte_eal/bsdapp/eal/eal_pci.c
index 7b04fa6..64bdea0 100644
--- a/lib/librte_eal/bsdapp/eal/eal_pci.c
+++ b/lib/librte_eal/bsdapp/eal/eal_pci.c
@@ -362,13 +362,13 @@ pci_scan_one(int dev_pci_fd, struct pci_conf *conf)
 	}
 
 	/* device is valid, add in list (sorted) */
-	if (TAILQ_EMPTY(&device_list)) {
-		TAILQ_INSERT_TAIL(&device_list, dev, next);
+	if (TAILQ_EMPTY(&pci_device_list)) {
+		TAILQ_INSERT_TAIL(&pci_device_list, dev, next);
 	}	
 	else {
 		struct rte_pci_device *dev2 = NULL;
 
-		TAILQ_FOREACH(dev2, &device_list, next) {
+		TAILQ_FOREACH(dev2, &pci_device_list, next) {
 			if (pci_addr_comparison(&dev->addr, &dev2->addr))
 				continue;
 			else {
@@ -376,7 +376,7 @@ pci_scan_one(int dev_pci_fd, struct pci_conf *conf)
 				return 0;
 			}
 		}
-		TAILQ_INSERT_TAIL(&device_list, dev, next);
+		TAILQ_INSERT_TAIL(&pci_device_list, dev, next);
 	}
 				
 	return 0;
@@ -503,8 +503,8 @@ rte_eal_pci_probe_one_driver(struct rte_pci_driver *dr, struct rte_pci_device *d
 int
 rte_eal_pci_init(void)
 {
-	TAILQ_INIT(&driver_list);
-	TAILQ_INIT(&device_list);
+	TAILQ_INIT(&pci_driver_list);
+	TAILQ_INIT(&pci_device_list);
 	uio_res_list = RTE_TAILQ_RESERVE_BY_IDX(RTE_TAILQ_PCI, uio_res_list);
 
 	/* for debug purposes, PCI can be disabled */
-- 
1.9.2

  reply	other threads:[~2014-04-25 12:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-25 11:59 [dpdk-dev] [PATCH 00/10] bsd: fix compilation Olivier Matz
2014-04-25 11:59 ` Olivier Matz [this message]
2014-04-25 11:59 ` [dpdk-dev] [PATCH 02/10] bsd/devargs: introduce API and test Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 03/10] bsd/devargs: use devargs for vdev and PCI whitelist/blacklist Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 04/10] bsd/devargs: use a comma instead of semicolon to separate key/values Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 05/10] bsd/devargs: replace --use-device option by --pci-whitelist and --vdev Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 06/10] bsd/devargs: allow to provide arguments per pci device Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 07/10] bsd/nic_uio: fix module compilation with freebsd 10 Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 08/10] bsd/mk: use the Q variable instead of @ for quiet commands Olivier Matz
2014-04-25 13:19   ` Neil Horman
2014-04-25 14:18     ` Thomas Monjalon
2014-04-25 11:59 ` [dpdk-dev] [PATCH 09/10] bsd/mem: get hugepages config Olivier Matz
2014-04-25 11:59 ` [dpdk-dev] [PATCH 10/10] bsd/mem: get physical address of any pointer Olivier Matz
2014-04-25 13:27 ` [dpdk-dev] [PATCH 00/10] bsd: fix compilation Neil Horman
2014-04-29 23:37   ` 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=1398427188-14914-2-git-send-email-olivier.matz@6wind.com \
    --to=olivier.matz@6wind.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).