On Wed, Jun 07, 2017 at 07:30:43AM +0000, Amrani, Ram wrote: > > Two options, > > > > 1) The 'ofed' approach: just use the latest rdma-core. We want > > rdma-core to run on any kernel version and any distro release, so > > this should not be a major problem > > My major concern was that when it comes to distros we don't have their > exact code base and/or can't release it. They take rdma-core X and > apply patches on it so it becomes rdma-core X.Y. All distros I know of provide full source - GPL requires it for most packages, and you would have a right to redistibute it, of course.. This is no different than the kernel. > Assuming backward-and-forward support, I might as well take rdma-core X+1 > and base upon it my newer patches. Right, that is what I ment when I said 'latest rdma-core' The very best thing you can do for your cusomters is to provide your changes in a way that the distro itself would be willing to backport and release as a minor update to their users. eg provide clear commit messages, a fixes tag, content that is appropriate for stable backporting and inform the distro via your corporate relationship to take the patch. This is what Leon is talking about. This is no different than the process for the kernel. Jason -- 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
