linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruce Fields <bfields@fieldses.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Bruce Fields <bfields@redhat.com>,
	Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH v1 0/2] Update synopsis of .pc_decode callback
Date: Wed, 13 Oct 2021 10:35:01 -0400	[thread overview]
Message-ID: <20211013143501.GB6260@fieldses.org> (raw)
In-Reply-To: <4F65A128-3DCC-4E8A-A7EE-5143152095C5@oracle.com>

On Wed, Oct 13, 2021 at 02:33:46PM +0000, Chuck Lever III wrote:
> 
> 
> > On Oct 13, 2021, at 10:31 AM, J. Bruce Fields <bfields@fieldses.org> wrote:
> > 
> > On Tue, Oct 12, 2021 at 11:57:15AM -0400, Chuck Lever wrote:
> >> As we discussed many moons ago, here are clean-up patches that
> >> modernize the .pc_decode callback's synopsis, based on the
> >> recent XDR overhaul work.
> > 
> > Looks sensible to me.
> > 
> > Applying pending some testing.
> 
> Thanks, Bruce.
> 
> I have similar patches for .pc_encode. Do you want to test those
> at the same time?

Sure, up to you.

(Not doing anything fancy, just my routine chton/xfstests/pynfs run).

--b.

      reply	other threads:[~2021-10-13 14:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-12 15:57 [PATCH v1 0/2] Update synopsis of .pc_decode callback Chuck Lever
2021-10-12 15:57 ` [PATCH v1 1/2] SUNRPC: Replace the "__be32 *p" parameter to .pc_decode Chuck Lever
2021-10-12 15:57 ` [PATCH v1 2/2] SUNRPC: Change return value type of .pc_decode Chuck Lever
2021-10-13 14:31 ` [PATCH v1 0/2] Update synopsis of .pc_decode callback J. Bruce Fields
2021-10-13 14:33   ` Chuck Lever III
2021-10-13 14:35     ` 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=20211013143501.GB6260@fieldses.org \
    --to=bfields@fieldses.org \
    --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;
as well as URLs for NNTP newsgroup(s).