Messages in this thread | | | Date | Wed, 8 Feb 2012 23:26:19 +0200 | Subject | Re: [PATCH] IB/ehca: use kthread_create_on_node | From | Or Gerlitz <> |
| |
On Thu, Feb 2, 2012 at 7:08 PM, Roland Dreier <roland@kernel.org> wrote: > On Thu, Feb 2, 2012 at 3:12 AM, Eric Dumazet <eric.dumazet@gmail.com> wrote:
>> Any news on this patch ?
> Sorry, just dropped it in the shuffle. I'll get it into 3.4, thanks.
Roland,
I noted that you typically use the for-next branch of the infiniband tree for fixes during the 1 < kernN-rc < (say) 6 time and for features during (kernN-rc > 6) till kern(N+1)-rc1
This means that the window of time when features are actually accepted into your tree is kind of very limited. Would it be possible to maintain two branches: for-next and (say) rc-fixes, such that practically patches are reviewed/accepted to for-next at almost all times?
BTW I see that networking and scsi maintainers use two trees (net/net-next) and (scsi-misc/scsi-rc-fixes), maybe it would be eaiser for you go this way?
Or. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |