From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Hemminger Subject: Re: [PATCH v7 6/6] devargs: parse bus info Date: Wed, 5 Jul 2017 11:03:48 -0700 Message-ID: <20170705110348.08a9ce7a@xeon-e3> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org To: Gaetan Rivet Return-path: Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by dpdk.org (Postfix) with ESMTP id 0CCB61C0B for ; Wed, 5 Jul 2017 20:03:55 +0200 (CEST) Received: by mail-pf0-f181.google.com with SMTP id c73so133338540pfk.2 for ; Wed, 05 Jul 2017 11:03:55 -0700 (PDT) In-Reply-To: List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On Wed, 5 Jul 2017 01:55:23 +0200 Gaetan Rivet wrote: > case RTE_DEVTYPE_WHITELISTED_PCI: > case RTE_DEVTYPE_BLACKLISTED_PCI: > /* try to parse pci identifier */ > - if (eal_parse_pci_BDF(buf, &devargs->pci.addr) != 0 && > - eal_parse_pci_DomBDF(buf, &devargs->pci.addr) != 0) > + if (bus->parse(devname, &devargs->pci.addr) != 0) > goto fail; Shouldn't these go under bus args for PCI? It would be good to get all the bus specific args out of generic code.