Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757390Ab2BHVfj (ORCPT ); Wed, 8 Feb 2012 16:35:39 -0500 Received: from mail-wi0-f174.google.com ([209.85.212.174]:57642 "EHLO mail-wi0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755839Ab2BHVfh (ORCPT ); Wed, 8 Feb 2012 16:35:37 -0500 MIME-Version: 1.0 In-Reply-To: References: <1311923731.7845.25.camel@edumazet-laptop> <1328181135.2279.9.camel@edumazet-HP-Compaq-6005-Pro-SFF-PC> From: Roland Dreier Date: Wed, 8 Feb 2012 13:35:16 -0800 X-Google-Sender-Auth: Cgoa0Th0qDzHx6dYqpIuU0IImnE Message-ID: Subject: Re: [PATCH] IB/ehca: use kthread_create_on_node To: Or Gerlitz Cc: Eric Dumazet , Sean Hefty , linux-rdma@vger.kernel.org, linux-kernel Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1534 Lines: 35 On Wed, Feb 8, 2012 at 1:26 PM, Or Gerlitz wrote: > 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? It's not really an issue of not having a tree to put things into. It's more that the window when I actually review major things is not as big as perhaps it should be. So I generally try to get fixes in expeditiously because they're easy to deal with, whereas I only dedicate time to merging bigger things when I feel the pressure of the impending merge window. I do usually have some small patches that are fine for the next window but which I have only marked "to apply" in my mailbox, which it might be a good idea to apply sooner so they get more -next tree coverage. - R. -- 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/