On 4/11/2017 4:44 PM, Gaetan Rivet wrote: > From: Jan Blunck <jblu...@infradead.org> > > In some cases the virtual device name should be totally different than > the driver being used for the device. Therefore lets parse the devargs for > the "driver" argument before probing drivers in vdev_probe_all_drivers().
Hi Gaetan, Jan, I have caught this while checking something else. This patch adds an alternative way for virtual devices to get probed when device name is not proper. This probing can be done by having "driver=<driver_name>" in device argument (not in name). Do we really need this alternative method, as far as I can see only user of this is a unit test for bonding? This method is a little hidden/undocumented and a hack solution, I think it is better and easier to fix virtual device names in unit test and remove this, what do you think? Thanks, ferruh > > Signed-off-by: Jan Blunck <jblu...@infradead.org> <...>
