From: cel@kernel.org
To: Trond Myklebust <trond.myklebust@hammerspace.com>,
Anna Schumaker <anna@kernel.org>
Cc: <linux-nfs@vger.kernel.org>, Chuck Lever <chuck.lever@oracle.com>,
Jeff Layton <jlayton@kernel.org>,
Benjamin Coddington <bcodding@redhat.com>,
Olga Kornievskaia <okorniev@redhat.com>
Subject: [PATCH v4 2/7] NFS: Fix typo in OFFLOAD_CANCEL comment
Date: Fri, 31 Jan 2025 19:34:42 -0500 [thread overview]
Message-ID: <20250201003447.54614-3-cel@kernel.org> (raw)
In-Reply-To: <20250201003447.54614-1-cel@kernel.org>
From: Chuck Lever <chuck.lever@oracle.com>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
Reviewed-by: Olga Kornievskaia <okorniev@redhat.com>
Tested-by: Olga Kornievskaia <okorniev@redhat.com>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
fs/nfs/nfs42xdr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nfs/nfs42xdr.c b/fs/nfs/nfs42xdr.c
index 9e3ae53e2205..ef5730c5e704 100644
--- a/fs/nfs/nfs42xdr.c
+++ b/fs/nfs/nfs42xdr.c
@@ -549,7 +549,7 @@ static void nfs4_xdr_enc_copy(struct rpc_rqst *req,
}
/*
- * Encode OFFLOAD_CANEL request
+ * Encode OFFLOAD_CANCEL request
*/
static void nfs4_xdr_enc_offload_cancel(struct rpc_rqst *req,
struct xdr_stream *xdr,
--
2.47.0
next prev parent reply other threads:[~2025-02-01 0:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 0:34 [PATCH v4 0/7] Client-side OFFLOAD_STATUS implementation cel
2025-02-01 0:34 ` [PATCH v4 1/7] NFS: CB_OFFLOAD can return NFS4ERR_DELAY cel
2025-02-01 0:34 ` cel [this message]
2025-02-01 0:34 ` [PATCH v4 3/7] NFS: Rename struct nfs4_offloadcancel_data cel
2025-02-01 0:34 ` [PATCH v4 4/7] NFS: Implement NFSv4.2's OFFLOAD_STATUS XDR cel
2025-02-01 0:34 ` [PATCH v4 5/7] NFS: Implement NFSv4.2's OFFLOAD_STATUS operation cel
2025-02-01 0:34 ` [PATCH v4 6/7] NFS: Use " cel
2025-02-01 0:34 ` [PATCH v4 7/7] NFS: Refactor trace_nfs4_offload_cancel cel
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=20250201003447.54614-3-cel@kernel.org \
--to=cel@kernel.org \
--cc=anna@kernel.org \
--cc=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=okorniev@redhat.com \
--cc=trond.myklebust@hammerspace.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.