On Thu, May 18, 2006 at 08:30:22AM +0300, Or Gerlitz wrote: > Please note that both approaches suggested above will not force to test > latest IB code with the under-development kernel...
Right. This is an open-source project. You can only "encourage" people to do one thing or another by making the integration harder or easier. And if it's too hard (ie get OFED bits that match a given kernel ABI), too many people just not bother. > So there's no replacement for testing done at least by the openib > maintainers (and distros!!! when they start moving to IB...) for: "at least by the openib maintainers" is a start but not sufficient. That's only a handful of people. > +1 next-kernel-RC-versions downloaded from kernel.org (eg 2.6.17-RCX) > +2 next-next-kernel-branches of infiniband.git (Roland's tree) > > Ofcourse people are busy, and testing is derived from needs.. Yes, people are busy. But people who only "need" are waiting for RHEL4u4, SLES10, et al and probably not even on this list. People who have time, _interest_, and HW usually end up "playing around" (ie testing) with bits if it's not too complicated. thanks, grant _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
