[dpdk-dev] [PATCH v4 2/2] bus/auxiliary: introduce auxiliary bus

Xueming(Steven) Li xuemingl at nvidia.com
Wed Jun 23 15:54:42 CEST 2021



> -----Original Message-----
> From: Thomas Monjalon <thomas at monjalon.net>
> Sent: Wednesday, June 23, 2021 4:22 PM
> To: Parav Pandit <parav at nvidia.com>; Xueming(Steven) Li <xuemingl at nvidia.com>
> Cc: dev at dpdk.org; Wang Haiyue <haiyue.wang at intel.com>; Kinsella Ray <mdr at ashroe.eu>; david.marchand at redhat.com;
> ferruh.yigit at intel.com
> Subject: Re: [dpdk-dev] [PATCH v4 2/2] bus/auxiliary: introduce auxiliary bus
> 
> 23/06/2021 01:50, Xueming(Steven) Li:
> > From: Thomas Monjalon <thomas at monjalon.net>
> > > 13/06/2021 14:58, Xueming Li:
> > > > +	struct rte_auxiliary_driver *driver;      /**< driver used in probing */
> > >
> > > Why in probing?
> > > I suggest "Device driver"
> >
> > A SF device could be probed by a class driver t then another class driver, the driver field will be overridden by later probe.
> > Will change to "last device driver"
> 
> "Last" is a bit confusing.
> Any field can be potentially overwritten, i.e. change its value, and we don't comment "last value" ;)

OK, will reflect in v6.



More information about the dev mailing list