From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Gunthorpe Subject: Re: [PATCH rdma-next v7 0/8] RDMA resource tracking Date: Tue, 30 Jan 2018 09:33:30 -0700 Message-ID: <20180130163330.GE17053@ziepe.ca> References: <20180128091725.13103-1-leon@kernel.org> <20180128210520.GK23869@ziepe.ca> <1517256713.27592.241.camel@redhat.com> <20180130033436.GA17053@ziepe.ca> <20180130091654.GD2055@mtr-leonro.local> <034101d399de$01183730$0348a590$@opengridcomputing.com> <20180130155643.GC17053@ziepe.ca> <035a01d399e5$9ed499d0$dc7dcd70$@opengridcomputing.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <035a01d399e5$9ed499d0$dc7dcd70$@opengridcomputing.com> Sender: linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Steve Wise Cc: 'Leon Romanovsky' , 'Doug Ledford' , 'RDMA mailing list' , 'Mark Bloch' List-Id: linux-rdma@vger.kernel.org On Tue, Jan 30, 2018 at 10:16:01AM -0600, Steve Wise wrote: > What is this a merge of exactly? I don't see the restrack stuff, for > instance. Yesterday's for-next. You could merge it with the latest for-next.. I updated it. I think we are done now, so for-next is what will be sent as the pull-request and for-next-merged is the conflict resolution. Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org More majordomo info at http://vger.kernel.org/majordomo-info.html