On Tue, Apr 3, 2012 at 11:38 PM, Or Gerlitz <ogerl...@mellanox.com> wrote: > On 4/2/2012 10:27 PM, Roland Dreier wrote: >> >> This looks reasonable, applied > > > Thanks, so we're in a situation where there are / will be fixes for 3.4 and > new code for 3.5 is coming, how about that suggestion I made lately - > for-next to contain code for the next kernel (e.g 3.5 at this point) and > have a different branch (maybe rc-fixes) to track fixes for the current > kernel (e.g 3.4)?
Yes, I am planning on doing that, and also never rebasing my for-next branch. - R. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
