linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: Or Gerlitz <ogerlitz@mellanox.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Chuck Lever <chuck.lever@oracle.com>,
	"J. Bruce Fields" <bfields@fieldses.org>,
	Doug Ledford <dledford@redhat.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org,
	LKML Kernel <linux-kernel@vger.kernel.org>,
	Ira Weiny <ira.weiny@intel.com>
Subject: Re: linux-next: manual merge of the rdma tree with the nfsd tree
Date: Wed, 6 Jan 2016 13:28:31 +0100	[thread overview]
Message-ID: <20160106122831.GA22044@lst.de> (raw)
In-Reply-To: <568D0711.5020607@mellanox.com>

On Wed, Jan 06, 2016 at 02:22:41PM +0200, Or Gerlitz wrote:
> As I wrote here, the bits are already @ kernel.org
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dledford/rdma.git k.o/for-4.5

Ok, that's a little confusing.

Doug, any chance you could settle on one tree? I don't really care
which one.

  reply	other threads:[~2016-01-06 12:28 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-31  2:30 linux-next: manual merge of the rdma tree with the nfsd tree Stephen Rothwell
2016-01-04  1:44 ` Stephen Rothwell
2016-01-04  2:53   ` Doug Ledford
2016-01-04 19:36     ` J. Bruce Fields
2016-01-06 12:01       ` Chuck Lever
2016-01-06 12:14         ` Or Gerlitz
2016-01-06 12:15         ` Christoph Hellwig
2016-01-06 12:22           ` Or Gerlitz
2016-01-06 12:28             ` Christoph Hellwig [this message]
2016-01-06 17:54               ` Doug Ledford
2016-01-06 14:24           ` Chuck Lever
2016-01-06 14:46             ` Or Gerlitz
2016-01-06 15:20               ` Chuck Lever
2016-01-06 15:52                 ` Or Gerlitz
2016-01-06 16:33                   ` Chuck Lever
2016-01-06 16:38                     ` Or Gerlitz
2016-01-06 16:48                     ` Anna Schumaker
2016-01-06 12:27         ` Chuck Lever
2016-01-06 16:25         ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160106122831.GA22044@lst.de \
    --to=hch@lst.de \
    --cc=bfields@fieldses.org \
    --cc=chuck.lever@oracle.com \
    --cc=dledford@redhat.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=ogerlitz@mellanox.com \
    --cc=sfr@canb.auug.org.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).