mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	linux-rdma <linux-rdma@vger.kernel.org>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	open list <linux-kernel@vger.kernel.org>,
	Trond Myklebust <trondmy@gmail.com>
Subject: Re: Please pull NFS server updates for v5.9
Date: Mon, 10 Aug 2020 09:03:49 +1000	[thread overview]
Message-ID: <20200810090349.64bce58f@canb.auug.org.au> (raw)
In-Reply-To: <F9B8940D-9F7B-47F5-9946-D77C17CF959A@oracle.com>

[-- Attachment #1: Type: text/plain, Size: 672 bytes --]

Hi Chuck,

On Sun, 9 Aug 2020 11:44:15 -0400 Chuck Lever <chuck.lever@oracle.com> wrote:
>
> The following changes since commit 11ba468877bb23f28956a35e896356252d63c983:
> 
>   Linux 5.8-rc5 (2020-07-12 16:34:50 -0700)
> 
> are available in the Git repository at:
> 
>   git://git.linux-nfs.org/projects/cel/cel-2.6.git tags/nfsd-5.9
> 
> for you to fetch changes up to b297fed699ad9e50315b27e78de42ac631c9990d:
> 
>   svcrdma: CM event handler clean up (2020-07-28 10:18:15 -0400)

Despite you having a branch included in linux-next, only one of these
commits has been in linux-next :-( (and that via Trond's nfs tree)

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-08-09 23:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-09 15:44 Chuck Lever
2020-08-09 23:03 ` Stephen Rothwell [this message]
2020-08-10 12:25   ` Chuck Lever
2020-08-11  6:15     ` Stephen Rothwell
2020-08-11 13:19       ` Chuck Lever

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=20200810090349.64bce58f@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chuck.lever@oracle.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trondmy@gmail.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

all inboxes | Powered by JetHome®