Lets bring this to the meting today I actually wanted to propose to delay 1.5 since 1.4.1 was delayed. In any case - if the EoIB code will not be ready it will not be in 1.5
Tziporet -----Original Message----- From: Woodruff, Robert J [mailto:robert.j.woodr...@intel.com] Sent: Monday, May 04, 2009 2:22 AM To: Or Gerlitz Cc: Roland Dreier (rdreier); ewg; Tziporet Koren Subject: RE: features / freeze I'll let Tziporet answer that one, since OFED 1.4.1 is dragging on a bit, perhaps OFED 1.5 feature freeze may also be delayed a bit so that people have time to get all the new code reviewed and such. woody -----Original Message----- From: Or Gerlitz [mailto:ogerl...@voltaire.com] Sent: Saturday, May 02, 2009 11:01 PM To: Woodruff, Robert J Cc: Roland Dreier (rdreier); ewg Subject: Re: features / freeze Woodruff, Robert J wrote: > Yes, in general we have agreed in the EWG that any code that goes into OFED should first be reviewed and accepted for upstream inclusion (or at least be accepted by Roland for a future kernel.org kernel.) before it goes into OFED. Given that the feature freeze for OFED 1.5 is coming up pretty soon, I would suggest starting this process as soon as you can if you want > to try to get this driver into OFED 1.5 Hi Woody and the EWG, recalling our related thread from couples of weeks ago, I didn't see any sign for the IBoE nor EoIB code being sent to review for mainline inclusion - does it mean neither of them is planned for the coming release? Or. _______________________________________________ ewg mailing list ewg@lists.openfabrics.org http://lists.openfabrics.org/cgi-bin/mailman/listinfo/ewg