[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200602204354.39727fdd@canb.auug.org.au>
Date: Tue, 2 Jun 2020 20:43:54 +1000
From: Stephen Rothwell <sfr@...b.auug.org.au>
To: Max Gurtovoy <maxg@...lanox.com>
Cc: Jens Axboe <axboe@...nel.dk>, Doug Ledford <dledford@...hat.com>,
Jason Gunthorpe <jgg@...lanox.com>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Yamin Friedman <yaminf@...lanox.com>,
Israel Rukshin <israelr@...lanox.com>,
Christoph Hellwig <hch@....de>
Subject: Re: linux-next: manual merge of the block tree with the rdma tree
Hi Max,
On Tue, 2 Jun 2020 11:37:26 +0300 Max Gurtovoy <maxg@...lanox.com> wrote:
>
> On 6/2/2020 5:56 AM, Stephen Rothwell wrote:
>
> This looks good to me.
>
> Can you share a pointer to the tree so we'll test it in our labs ?
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
you want tag next-20200602
or if you just want that trees that conflicted, then
block: git://git.kernel.dk/linux-block.git branch for-next
rdma: git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma.git branch for-next
--
Cheers,
Stephen Rothwell
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists