From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jeff Layton <jlayton@primarydata.com>
Subject: Re: [GIT PULL] nfsd changes for 4.6
Date: Thu, 24 Mar 2016 15:10:59 -0400 [thread overview]
Message-ID: <20160324191059.GA23783@fieldses.org> (raw)
In-Reply-To: <CAHQdGtQWNaTVVBA7VxRHh2jmxCVO_7pMHXt6JEQsLr0K9TThtg@mail.gmail.com>
On Thu, Mar 24, 2016 at 03:00:55PM -0400, Trond Myklebust wrote:
> On Thu, Mar 24, 2016 at 9:35 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > Please pull nfsd changes for 4.6 from
> >
> > git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.6
> >
> > ----------------------------------------------------------------
> > Various bugfixes, a RDMA update from Chuck Lever, and support for a new
> > pnfs layout type from Christoph Hellwig. The new layout type is a
> > variant of the block layout which uses SCSI features to offer improved
> > fencing and device identification.
> >
> > (Also: note this pull request also includes the client side of SCSI
> > layout, with Trond's permission.)
>
> Umm.... Did you forget to include those patches, Bruce?
Oh no, I forgot to update a branch before running my usual script so,
yes, that tag's a subset of what I meant to send.
Uh, I guess what I'll do is push an nfsd-4.6-1 tag with the rest. Linus
can either pull both tags or just the new one and hopefully the result's
OK either way. Just a couple minutes....
--b.
prev parent reply other threads:[~2016-03-24 19:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 13:35 [GIT PULL] nfsd changes for 4.6 J. Bruce Fields
2016-03-24 19:00 ` Trond Myklebust
2016-03-24 19:10 ` J. Bruce Fields [this message]
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=20160324191059.GA23783@fieldses.org \
--to=bfields@fieldses.org \
--cc=jlayton@primarydata.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=trond.myklebust@primarydata.com \
/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).