Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-15 Thread Thomas Monjalon
10/07/2022 08:17, David Marchand: > rte_driver and rte_device are unnecessarily exposed in the public API/ABI. > Announce that they will be made opaque in the public API and mark > associated API as internal. > This impacts all bus, as their driver registration mechanism will be > made internal. >

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-12 Thread Andrew Rybchenko
On 7/12/22 11:24, Kevin Laatz wrote: On 10/07/2022 07:17, David Marchand wrote: rte_driver and rte_device are unnecessarily exposed in the public API/ABI. Announce that they will be made opaque in the public API and mark associated API as internal. This impacts all bus, as their driver registra

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-12 Thread Kevin Laatz
On 10/07/2022 07:17, David Marchand wrote: rte_driver and rte_device are unnecessarily exposed in the public API/ABI. Announce that they will be made opaque in the public API and mark associated API as internal. This impacts all bus, as their driver registration mechanism will be made internal.

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-11 Thread Hemant Agrawal
On 7/10/2022 11:47 AM, David Marchand wrote: rte_driver and rte_device are unnecessarily exposed in the public API/ABI. Announce that they will be made opaque in the public API and mark associated API as internal. This impacts all bus, as their driver registration mechanism will be made interna

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-11 Thread Jerin Jacob
On Sun, Jul 10, 2022 at 11:48 AM David Marchand wrote: > > rte_driver and rte_device are unnecessarily exposed in the public API/ABI. > Announce that they will be made opaque in the public API and mark > associated API as internal. > This impacts all bus, as their driver registration mechanism wil

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-11 Thread Thomas Monjalon
11/07/2022 04:16, Xia, Chenbo: > From: David Marchand > > rte_driver and rte_device are unnecessarily exposed in the public API/ABI. > > Announce that they will be made opaque in the public API and mark > > associated API as internal. > > This impacts all bus, as their driver registration mechanis

RE: [PATCH] doc: announce marking device and driver objects as internal

2022-07-10 Thread Xia, Chenbo
Hi David, > -Original Message- > From: David Marchand > Sent: Sunday, July 10, 2022 2:18 PM > To: dev@dpdk.org; techbo...@dpdk.org > Cc: Ray Kinsella > Subject: [PATCH] doc: announce marking device and driver objects as > internal > > rte_driver and rte_devic

Re: [PATCH] doc: announce marking device and driver objects as internal

2022-07-10 Thread Andrew Rybchenko
On 7/10/22 09:17, David Marchand wrote: rte_driver and rte_device are unnecessarily exposed in the public API/ABI. Announce that they will be made opaque in the public API and mark associated API as internal. This impacts all bus, as their driver registration mechanism will be made internal. Not

[PATCH] doc: announce marking device and driver objects as internal

2022-07-09 Thread David Marchand
rte_driver and rte_device are unnecessarily exposed in the public API/ABI. Announce that they will be made opaque in the public API and mark associated API as internal. This impacts all bus, as their driver registration mechanism will be made internal. Note: the PCI bus had a similar deprecation n