RE: [PATCH] doc: announce some raw/ifpga API removal

["Huang, Wei" <wei.huang@intel.com>]

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Thursday, July 7, 2022 17:30
> To: Huang, Wei <wei.huang@intel.com>; Zhang, Tianfei
> <tianfei.zhang@intel.com>; Xu, Rosen <rosen.xu@intel.com>
> Cc: dev@dpdk.org; Ray Kinsella <mdr@ashroe.eu>
> Subject: Re: [PATCH] doc: announce some raw/ifpga API removal
> 
> On Fri, Jul 1, 2022 at 10:35 AM David Marchand <david.marchand@redhat.com>
> wrote:
> > > > > > > Can't this application use rte_dev_remove and rte_dev_probe?
> > > > > > > If not, we should add the missing parts in the API.
> > > > > > >
> > > > > > Both rte_dev_remove and rte_dev_probe need rte_device pointer.
> > > > > > In this application, it only know the device's PCI address, is
> > > > > > there an existing API
> > > > to get the rte_pci_device pointer by its PCI address ?
> > > > >
> > > > > rte_dev_probe takes a devargs string as input.
> > > > > int rte_dev_probe(const char *devargs);
> > > > >
> > > > > You need the rte_device for removing which can be retrieved from
> > > > > rte_rawdev_info_get.
> > > >
> > > > Additionnaly, rte_eal_hotplug_{add,remove} do the same jobs, but
> > > > with an
> > > > easier(?) interface.
> > > >
> > > >
> > > I checked rte_eal_hotplug_{add,remove}, they should meet my requirements,
> thanks a lot.
> >
> > Cool, thanks.
> 
> So it seems there is nothing blocking for this API change.
> Could you ack the deprecation notice?
> 
This API can be removed.
Acked

> Thanks.
> 
> --
> David Marchand