From: Jeff Kirsher <jeffrey.t.kirs...@intel.com> Date: Tue, 18 Sep 2018 15:37:17 -0700
> This series contains changes to i40evf so that it becomes a more > generic virtual function driver for current and future silicon. > > While doing the rename of i40evf to a more generic name of iavf, > we also put the driver on a severe diet due to how much of the > code was unneeded or was unused. The outcome is a lean and mean > virtual function driver that continues to work on existing 40GbE > (i40e) virtual devices and prepped for future supported devices, > like the 100GbE (ice) virtual devices. > > This solves 2 issues we saw coming or were already present, the > first was constant code duplication happening with i40e/i40evf, > when much of the duplicate code in the i40evf was not used or was > not needed. The second was to remove the future confusion of why > future VF devices that were not considered "40GbE" only devices > were supported by i40evf. > > The thought is that iavf will be the virtual function driver for > all future devices, so it should have a "generic" name to properly > represent that it is the VF driver for multiple generations of > devices. > > The last patch in this series is unreleated to the iavf conversion > and just has to do with a MODULE_LICENSE correction. > > Known Caveats: > Existing user space configurations may have to change, but the module > alias in patch 1 helps a bit here. Ok, let's see how this goes. Pulled, thanks.
