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,
Tziporet Koren wrote:
In any case - if the EoIB code will not be ready it will not be in 1.5
Unlike the IBoE patchset, EoIB is more of a stand alone in the sense
that it adds a driver to the IB stack and generally speaking doesn't
touch other components, where the IBoE patches touch many
We will send the code to review when its ready.
Tziporet
-Original Message-
From: Or Gerlitz [mailto:ogerl...@voltaire.com]
Sent: Monday, May 04, 2009 12:49 PM
To: Tziporet Koren
Cc: Woodruff, Robert J; Roland Dreier (rdreier); ewg
Subject: Re: features / freeze
Tziporet Koren wrote:
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
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:
