mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chuck Lever <chuck.lever@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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: Tue, 11 Aug 2020 09:19:03 -0400	[thread overview]
Message-ID: <5D3B9AC6-6A27-4795-A256-C9CE0D459D15@oracle.com> (raw)
In-Reply-To: <20200811161518.0896c1e8@canb.auug.org.au>



> On Aug 11, 2020, at 2:15 AM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> Hi Chuck,
> 
> On Mon, 10 Aug 2020 08:25:14 -0400 Chuck Lever <chuck.lever@oracle.com> wrote:
>> 
>> Is there something I need to change? The public copy of the cel-testing
>> branch has had this content for the past 12 days.
> 
> You just need to keep your cel-next branch up to the top commit that is
> ready.  That is the branch you told me to fetch.  It is currently at commit
> 
>  0a8e7b7d0846 ("SUNRPC: Revert 241b1f419f0e ("SUNRPC: Remove xdr_buf_trim()")")
> 
> It looks like that is what Linus merged into v5.7-rc2.

Ah. I thought you were pulling cel-testing, so I deleted cel-next. I will
rehydrate cel-next right now.

--
Chuck Lever




      reply	other threads:[~2020-08-11 13:19 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
2020-08-10 12:25   ` Chuck Lever
2020-08-11  6:15     ` Stephen Rothwell
2020-08-11 13:19       ` Chuck Lever [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=5D3B9AC6-6A27-4795-A256-C9CE0D459D15@oracle.com \
    --to=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=sfr@canb.auug.org.au \
    --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®