Linux NFS development
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	Jeff Layton <jlayton@redhat.com>
Subject: Re: [GIT PULL] nfsd changes for 4.14-rc
Date: Tue, 10 Oct 2017 15:27:06 -0400	[thread overview]
Message-ID: <20171010192706.GA18513@fieldses.org> (raw)
In-Reply-To: <CA+55aFz5vGYnwzZ5mMQz5PXXRaMd3RaDF_fe11WKRDzWJCahJQ@mail.gmail.com>

On Tue, Oct 10, 2017 at 11:42:01AM -0700, Linus Torvalds wrote:
> On Tue, Oct 10, 2017 at 11:24 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > Please pull nfsd fixes from
> >
> >   git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.14-1
> 
> There's nothing there. That tag just points to my 4.14-rc1 commit.
> 
> > One fix for a 4.14 regression, and one minor fix to the MAINTAINERs
> > file. (I was weirdly flattered by the idea that lots of random people
> > suddenly seemed to think Jeff and I were VFS experts.  Turns out it was
> > just a typo.)
> 
> .. and there's also no diffstat and commit list in your pull request,
> probably exactly because you screwed up the tag so there's nothing to
> pull..

Sigh, so it's not like I didn't have enough warning signs.

I just deleted redid the tag with the same name.  (Does it cause a
problem that the old object is still sitting around somewhere with the
same name but nothing pointing at it?  I'm assuming not.)

--b.

  git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.14-1

----------------------------------------------------------------
One fix for a 4.14 regression, and one minor fix to the MAINTAINERs
file. (I was weirdly flattered by the idea that lots of random people
suddenly seemed to think Jeff and I were VFS experts.  Turns out it was
just a typo.)

----------------------------------------------------------------
Eric Biggers (1):
      MAINTAINERS: associate linux/fs.h with VFS instead of file locking

Eryu Guan (1):
      nfsd4: define nfsd4_secinfo_no_name_release()

 MAINTAINERS        | 4 ++--
 fs/nfsd/nfs4proc.c | 9 ++++++++-
 2 files changed, 10 insertions(+), 3 deletions(-)

  reply	other threads:[~2017-10-10 19:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-10 18:24 [GIT PULL] nfsd changes for 4.14-rc J. Bruce Fields
2017-10-10 18:42 ` Linus Torvalds
2017-10-10 19:27   ` J. Bruce Fields [this message]
2017-10-10 20:02     ` Linus Torvalds

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=20171010192706.GA18513@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=jlayton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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