Jason wrote, >One of the best ways to get it tested is to get it to go through the full OFED process. >Woody, what could we do to help make that happen? Do you know of any blocker? >I think this will be the best for everyone. I also predict that OFED will be under pressure to quickly take up the new drivers that will land in >4.9, and their user space will live in rdma-core. >I also propose we give someone from the OFED team repo access and they can maintain a public branch for ofed-4.8 with any backported >fixes. >Jason We have just started work on OFED-4.8, so there is still a possibility to move to the new tree as the basis for the user-space code that that goes into OFED. I think that Vlad (who is the OFED integration engineer) was waiting till things were a little more finalized and wait till all packaging was flushed out before moving to the new code base. I think it would be desirable if there were some kind of official release tar ball or at least official release git tag that is recommended by you guys that we should use in OFED. Currently the way OFED handles user-space packages is that we wait till the maintainer of a user-space package produces a release for their user-space component, which is a tar ball with the spec files that can be used to produce SRPMS. I have not followed this really closely, but have you guys finalized how the packaging in SRPMs will/should work ? Or is that an exercise left up to the Linux distros and/or OFED to decide on ? In any case, Vlad is on vacation for a couple weeks, so he probably cannot re-look at this until after Nov 1 when he returns, so you have some time to decide on how you want to handle releases for this. woody -- 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
