public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "olga.kornievskaia@gmail.com" <olga.kornievskaia@gmail.com>
Cc: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
	"anna.schumaker@netapp.com" <anna.schumaker@netapp.com>,
	"chuck.lever@oracle.com" <chuck.lever@oracle.com>
Subject: Re: [PATCH 1/1] NFSv4.1+ add trunking when server trunking detected
Date: Tue, 8 Jun 2021 23:12:13 +0000	[thread overview]
Message-ID: <c59a989f47e507170320e1b9ee9ca6854b05ef08.camel@hammerspace.com> (raw)
In-Reply-To: <27a8050d05d12a2bd294fe0b035ad7a39e63aaca.camel@hammerspace.com>

On Tue, 2021-06-08 at 23:02 +0000, Trond Myklebust wrote:
> Sorry. I should have written: 'rpc_clnt_add_xprt() with
> rpc_clnt_setup_test_and_add_xprt()', which is what pNFS uses when

Growl... My keyboard is hexed today. I mean 'rpc_clnt_add_xprt() with
rpc_clnt_test_and_add_xprt'.

> connecting to NFSv3 servers.
> i.e.
> 
>    rpc_clnt_add_xprt(clp->cl_rpcclient, &xprt_args,
>                      rpc_clnt_test_and_add_xprt, NULL);
> 

The above line is correct...

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



  reply	other threads:[~2021-06-08 23:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-08 18:45 [PATCH 1/1] NFSv4.1+ add trunking when server trunking detected Olga Kornievskaia
2021-06-08 20:41 ` Chuck Lever III
2021-06-08 20:56   ` Olga Kornievskaia
2021-06-08 21:06     ` Chuck Lever III
2021-06-08 21:19       ` Trond Myklebust
2021-06-08 21:26         ` Trond Myklebust
2021-06-08 21:30           ` Olga Kornievskaia
2021-06-08 21:41             ` Trond Myklebust
2021-06-08 22:21               ` Olga Kornievskaia
2021-06-08 22:31                 ` Trond Myklebust
2021-06-08 22:38                   ` Olga Kornievskaia
2021-06-08 23:02                     ` Trond Myklebust
2021-06-08 23:12                       ` Trond Myklebust [this message]
2021-06-08 21:40       ` Olga Kornievskaia
2021-06-08 22:13         ` Trond Myklebust
2021-06-08 22:18           ` Olga Kornievskaia
2021-06-08 22:27             ` Trond Myklebust
2021-06-08 22:38               ` Olga Kornievskaia
2021-06-08 22:58                 ` Trond Myklebust
2021-06-09 20:47       ` Olga Kornievskaia
2021-06-08 22:39 ` kernel test robot
2021-06-08 23:36 ` kernel test robot

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=c59a989f47e507170320e1b9ee9ca6854b05ef08.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --cc=anna.schumaker@netapp.com \
    --cc=chuck.lever@oracle.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=olga.kornievskaia@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