From: kernel test robot <lkp@intel.com>
To: "D. Wythe" <alibuda@linux.alibaba.com>, kgraul@linux.ibm.com
Cc: kbuild-all@lists.01.org, kuba@kernel.org, davem@davemloft.net,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux-rdma@vger.kernel.org,
"D. Wythe" <alibuda@linux.alibaba.com>
Subject: [RFC PATCH] net/smc: smc_tcp_ls_wq can be static
Date: Sat, 5 Feb 2022 20:09:48 +0800 [thread overview]
Message-ID: <20220205120947.GA10751@d01e203e4d07> (raw)
In-Reply-To: <1d7365b47719546fe1f145affb01398d8287b381.1644041638.git.alibuda@linux.alibaba.com>
net/smc/af_smc.c:62:25: warning: symbol 'smc_tcp_ls_wq' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
af_smc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/smc/af_smc.c b/net/smc/af_smc.c
index 05b88cbadf3d1..4969ac8029a98 100644
--- a/net/smc/af_smc.c
+++ b/net/smc/af_smc.c
@@ -59,7 +59,7 @@ static DEFINE_MUTEX(smc_client_lgr_pending); /* serialize link group
* creation on client
*/
-struct workqueue_struct *smc_tcp_ls_wq; /* wq for tcp listen work */
+static struct workqueue_struct *smc_tcp_ls_wq; /* wq for tcp listen work */
struct workqueue_struct *smc_hs_wq; /* wq for handshake work */
struct workqueue_struct *smc_close_wq; /* wq for close work */
next prev parent reply other threads:[~2022-02-05 12:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-05 6:34 [PATCH net-next v3 0/3] Optimizing performance in short-lived scenarios D. Wythe
2022-02-05 6:34 ` [PATCH net-next v3 1/3] net/smc: Make smc_tcp_listen_work() independent D. Wythe
2022-02-05 12:09 ` kernel test robot [this message]
2022-02-05 12:16 ` kernel test robot
2022-02-05 6:34 ` [PATCH net-next v3 2/3] net/smc: Limits backlog connections D. Wythe
2022-02-05 6:34 ` [PATCH net-next v3 3/3] net/smc: Fallback when handshake workqueue congested D. Wythe
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=20220205120947.GA10751@d01e203e4d07 \
--to=lkp@intel.com \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=kbuild-all@lists.01.org \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@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).