On Wed, Jun 16, 2010 at 09:09:59AM -0500, Steve Wise wrote: > Granted our dev process may not be documented, but I always assumed the > general idea was to get changes accepted upstream, then pull into ofed. > OFED is just a mechanism to make top-of-tree linux work on distro > kernels. There are some exceptions, but this stuff shouldn't be an > exception.
That is what many people wish for, me included, but it is not at all what generally happens :( In my observation the typical flow is: - A patch is written, it may or may not be sent to the list - 'business drivers' get it slammed into OFED right away - A patch is finally sent for proper review - It is not merged, there are comments.. - Interest in doing anything is lost because it is already in OFED and that is all that matters, right? - People complain. For instance, the iWarp thingy we were just discussing fits this process rather well. Jason _______________________________________________ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg