From: Jeff Layton <jlayton@redhat.com>
To: Chuck Lever <chuck.lever@oracle.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Bruce Fields <bfields@redhat.com>
Subject: Re: NFSD merge candidate for v5.11
Date: Tue, 24 Nov 2020 18:14:14 -0500 [thread overview]
Message-ID: <0cbeed0a0fa2352961966efdd7e62247b5cd7a7b.camel@redhat.com> (raw)
In-Reply-To: <48FA73BE-2D86-4A3F-91D5-C1086E228938@oracle.com>
On Tue, 2020-11-24 at 17:51 -0500, Chuck Lever wrote:
> Hi-
>
> I've added my NFSv4 XDR decoder series and Bruce's iversion
> series to my "for next" topic branch to get some early
> testing exposure for these changes.
>
> Bruce's series is based on 8/8 posted on November 20, with
> Jeff's review comments integrated. The NFSD XDR decoder
> patches are based on v4, posted yesterday afternoon with
> Bruce's review comments integrated.
>
> The full branch is available here:
>
> git://git.linux-nfs.org/projects/cel/cel-2.6.git cel-next
>
> or
>
> http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=shortlog;h=refs/heads/cel-next
>
> ...and is still open for changes or additional patches. This
> branch is pulled into linux-next regularly.
>
>
Minor nit in:
http://git.linux-nfs.org/?p=cel/cel-2.6.git;a=commit;h=2513716015eba398378bf453d5d2dd46c63a3399
You added a generic_check_iversion prototype to fs.h.
Move that into iversion.h. I think it makes more sense there, and that
avoids the huge rebuild that occurs when fs.h changes.
Cheers!
--
Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2020-11-24 23:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 22:51 NFSD merge candidate for v5.11 Chuck Lever
2020-11-24 23:14 ` Jeff Layton [this message]
2020-11-25 0:36 ` Chuck Lever
2020-11-25 14:56 ` J. Bruce Fields
2020-11-30 19:47 ` 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=0cbeed0a0fa2352961966efdd7e62247b5cd7a7b.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=bfields@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.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