On Thu, Oct 29, 2015 at 4:16 PM, Doug Ledford <dledford@xxxxxxxxxx> wrote: > On 10/29/2015 01:42 AM, Or Gerlitz wrote: >> On Thu, Oct 29, 2015 at 4:34 AM, Doug Ledford <dledford@xxxxxxxxxx> wrote: >>> Yes, I've pulled this in for 4.4. Thanks! >> >> Doug, we want to run regression over the 4.4 bits, when do you expect >> for them to show up @ your kernel.org tree? > > Sorry, when the fast registration API caused compile failure yesterday I > stopped at it and forgot to push the result out. So, I've removed the > last patch of that series so it resolves the build breakage for now. We > can add the last patch back in after the staging drivers are fixed up. > The result has been pushed to both github and k.o. > >> some of them are there but >> @ least 3-4 series which you said "applied" aren't, AFAIR last time it >> was only about whole ten days after the merge window opened. Also, >> without the patches being there the code isn't subject to linux-next >> merge test (also after being there neither, since the branch name >> changes for each release and I didn't see you setting a flying tag, or >> you did so?) > > Yes, I set a flying tag as you call it. Doug, can you please re-spare few words on how this works? Stephen, is the framework for linux-next merge tests OK with this tag? can you confirm that the -next bits of the rdma tree are covered fine? Alaa, are you managing to follow on this tag for the MLNX internal builds? or you use manually the k.o/4.4 branch? Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
