> -Original Message-
> From: Thomas Monjalon [mailto:thomas.monja...@6wind.com]
> Sent: Wednesday, February 15, 2017 4:53 PM
> To: Jan Blunck ; Shreyansh Jain
>
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v11 07/13] pci: split match and probe
>
> 2
On Wednesday 15 February 2017 04:15 PM, Jan Blunck wrote:
On Thu, Jan 19, 2017 at 5:45 AM, Thomas Monjalon
wrote:
From: Shreyansh Jain
Matching of PCI device address and driver ID table is being done at two
discreet locations duplicating the code. (rte_eal_pci_probe_one_driver
and rte_eal_pci
2017-02-15 11:45, Jan Blunck:
> > /**
> > + * Match the PCI Driver and Device using the ID Table
> > + *
> > + * @param pci_drv
> > + * PCI driver from which ID table would be extracted
> > + * @param pci_dev
> > + * PCI device to match against the driver
> > + * @return
> > + * 0 for
On Thu, Jan 19, 2017 at 5:45 AM, Thomas Monjalon
wrote:
> From: Shreyansh Jain
>
> Matching of PCI device address and driver ID table is being done at two
> discreet locations duplicating the code. (rte_eal_pci_probe_one_driver
> and rte_eal_pci_detach_dev).
>
> Splitting the matching function in
From: Shreyansh Jain
Matching of PCI device address and driver ID table is being done at two
discreet locations duplicating the code. (rte_eal_pci_probe_one_driver
and rte_eal_pci_detach_dev).
Splitting the matching function into a public fn rte_pci_match.
Signed-off-by: Shreyansh Jain
Reviewe
5 matches
Mail list logo