From: Haiyue Wang <haiyue.wang@intel.com>
To: netdev@vger.kernel.org, lixiaoyan@google.com
Cc: Haiyue Wang <haiyue.wang@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org (open list:DOCUMENTATION),
linux-kernel@vger.kernel.org (open list)
Subject: [PATCH net v1] Documentations: correct net_cachelines title for struct inet_sock
Date: Fri, 23 Feb 2024 20:02:12 +0800 [thread overview]
Message-ID: <20240223120215.2300560-1-haiyue.wang@intel.com> (raw)
It's 'inet_sock' fast path usage breakdown, not 'inet_connection_sock',
correct it.
Signed-off-by: Haiyue Wang <haiyue.wang@intel.com>
---
Documentation/networking/net_cachelines/inet_sock.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/networking/net_cachelines/inet_sock.rst b/Documentation/networking/net_cachelines/inet_sock.rst
index a2babd0d7954..868361b4792d 100644
--- a/Documentation/networking/net_cachelines/inet_sock.rst
+++ b/Documentation/networking/net_cachelines/inet_sock.rst
@@ -2,7 +2,7 @@
.. Copyright (C) 2023 Google LLC
=====================================================
-inet_connection_sock struct fast path usage breakdown
+inet_sock struct fast path usage breakdown
=====================================================
Type Name fastpath_tx_access fastpath_rx_access comment
--
2.43.2
next reply other threads:[~2024-02-23 11:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 12:02 Haiyue Wang [this message]
2024-02-26 16:24 ` [PATCH net v1] Documentations: correct net_cachelines title for struct inet_sock Jakub Kicinski
2024-02-26 16:57 ` [PATCH net v2] " Haiyue Wang
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=20240223120215.2300560-1-haiyue.wang@intel.com \
--to=haiyue.wang@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lixiaoyan@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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;
as well as URLs for NNTP newsgroup(s).