To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [git pull] InfiniBand updates for 2.6.14
References: <523bmlqkg0.fsf@cisco.com> <20051028171218.2b8e71e7.akpm@osdl.org>
From: Roland Dreier <rolandd@cisco.com>
Date: Fri, 28 Oct 2005 17:18:42 -0700
In-Reply-To: <20051028171218.2b8e71e7.akpm@osdl.org> (Andrew Morton's
 message of "Fri, 28 Oct 2005 17:12:18 -0700")
Message-ID: <52y84dp44d.fsf@cisco.com>
User-Agent: Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.17 (Jumbo Shrimp, linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 871
Lines: 21

    Andrew> a) arrange for the current infiniband devel tree to be
    Andrew> included in -mm and

Sure.  How do you want to handle that?  The way I've been working
lately is to merge things onto my "upstream" branch when I intend for
them to go to Linus eventually, and merge that onto the "for-linus"
branch when I'm going to ask Linus to pull.  I guess it would make
sense for you to grab the upstream branch for -mm.

    Andrew> b) arrange for infiniband patches to get wider review than this?

No objection from me.  How do you suggest I do that?  Post things to
linux-kernel as I merge them into git?

Thanks,
  Roland
-
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/