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)?
Or. -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
