On Thu, 2015-02-12 at 00:25 -0500, Or Gerlitz wrote: > On 2/11/2015 11:55 PM, Doug Ledford wrote: > > I tried, but the most appropriate squashes were things like patch 18 and > > 19 squashed into patch 3, and some other similar jumping around of > > patches. The number of conflicts that created in both the original > > squash and the follow on patches was perverse. So, since the original > > 20 patches as I submitted previously are what has gone through our QA, I > > left them as they were. If I fixed them up and squashed them, and if > > some overlooked fixup failure snuck in there, it would invalidate all of > > that testing. > > I see. Does this sequence bisect-able? namely the driver builds and > functions after applying patch by patch? note this is hard requirement > when modifying existing upstream drivers.
Yes. There might be some oddities in the behavior of the running IPoIB
driver specifically when testing the mcast abilities in the middle of
this patch set, but they will all build and function at a basic level.
--
Doug Ledford <dledf...@redhat.com>
GPG KeyID: 0E572FDD
signature.asc
Description: This is a digitally signed message part
