> From: Jeff Kirsher <jeffrey.t.kirsher@xxxxxxxxx> > Sent: Friday, November 15, 2019 4:34 PM > Subject: [net-next v2 1/1] virtual-bus: Implementation of Virtual Bus > > From: Dave Ertman <david.m.ertman@xxxxxxxxx> > > This is the initial implementation of the Virtual Bus, virtbus_device and > virtbus_driver. The virtual bus is a software based bus intended to support > lightweight devices and drivers and provide matching between them and When you wrote ' lightweight devices', you probably intent to say, 'multiple class of devices such as rdma, netdev etc for a single underlying parent device'. 'struct class' has clear meaning in kernel with above two examples and more. Though it's not limited to these two classes, an example is always better. :-) If so, please word that say, that avoids the confusion and it will be aligned to below primary purpose description. > probing of the registered drivers. > > The primary purpose of the virual bus is to provide matching services and to > pass the data pointer contained in the virtbus_device to the virtbus_driver > during its probe call. This will allow two separate kernel objects to match up > and start communication.
