All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Lever <cel@kernel.org>
To: linux-nfs@vger.kernel.org
Cc: Chuck Lever <chuck.lever@oracle.com>
Subject: [PATCH 1/4] SUNRPC: Fix an incorrect comment
Date: Mon, 15 May 2023 09:32:41 -0400	[thread overview]
Message-ID: <168415756128.9504.10972346476896238136.stgit@manet.1015granger.net> (raw)
In-Reply-To: <168415745478.9504.1882537002036193828.stgit@manet.1015granger.net>

From: Chuck Lever <chuck.lever@oracle.com>

The correct function name is svc_tcp_listen_data_ready().

Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
---
 net/sunrpc/svcsock.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/net/sunrpc/svcsock.c b/net/sunrpc/svcsock.c
index 9aca6e1e78e4..e0fb65e90af2 100644
--- a/net/sunrpc/svcsock.c
+++ b/net/sunrpc/svcsock.c
@@ -1469,7 +1469,7 @@ static struct svc_sock *svc_setup_socket(struct svc_serv *serv,
 	svsk->sk_owspace = inet->sk_write_space;
 	/*
 	 * This barrier is necessary in order to prevent race condition
-	 * with svc_data_ready(), svc_listen_data_ready() and others
+	 * with svc_data_ready(), svc_tcp_listen_data_ready(), and others
 	 * when calling callbacks above.
 	 */
 	wmb();



  reply	other threads:[~2023-05-15 13:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-15 13:32 [PATCH 0/4] Socket creation observability Chuck Lever
2023-05-15 13:32 ` Chuck Lever [this message]
2023-05-15 13:32 ` [PATCH 2/4] SUNRPC: Remove dprintk() in svc_handle_xprt() Chuck Lever
2023-05-15 13:32 ` [PATCH 3/4] SUNRPC: Improve observability in svc_tcp_accept() Chuck Lever
2023-05-15 16:54   ` Jeff Layton
2023-05-15 17:07     ` Chuck Lever III
2023-05-15 13:33 ` [PATCH 4/4] SUNRPC: Trace struct svc_sock lifetime events Chuck Lever
2023-05-15 16:56 ` [PATCH 0/4] Socket creation observability Jeff Layton
2023-05-15 18:10   ` Chuck Lever III

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=168415756128.9504.10972346476896238136.stgit@manet.1015granger.net \
    --to=cel@kernel.org \
    --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 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.