On Thu, Apr 12, 2018 at 03:56:42PM +0000, Sridhar Pitchai wrote: > > > > >> I am still not happy with this patch. > > >> > > >> - You do not explain at all the dependency on commit > 0c195567a8f6 and > > >> you should because that's fundamental, if that patch is not > present > > >> this revert breaks the kernel as per previous discussions. > > >> - You are sending this patch to all stable kernels that contain > the > > >> commit you are fixing - some that may not contain the commit > above > > >> (that was merged in v4.14), you are breaking those kernels, > if not > > >> explain me why please > > > > >If there's a dependency on 0c195567a8f6, I totally agree that > > >needs to be cleared up. I was assuming that turned out to be > > >irrelevant. > > That is right. There is no dependency on 0c195567a8f6. We just need to > revert > > 4a9b0933bdfc. > > > This patch should only be applied to later versions after > 0c195567a8f6" (transparent VF). > > Otherwise it causes long & random names of VF NICs for bonding. That > will make bonding > > config difficult, especially for auto config. > > >Thanks, > >- Haiyang > Ok. I will update the patch, as Lorenzo suggested.
Please update your email client quoting policy so that it does not add unnecessary indentation spaces, for long threads this gets messy. If you send a patch to a specific stable version you have to test it first thing on that stable version before adding a stable tag, reverting a patch from stable kernels is the last thing we want to do - that's the reason why I keep complaining. Thanks, Lorenzo _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel