Content-Type: multipart/mixed; boundary="===============6256344189066564390==" MIME-Version: 1.0 From: kernel test robot To: kbuild-all@lists.01.org Subject: [RFC PATCH] nvme-tcp-offload: nvme_tcp_ofld_lookup_dev can be static Date: Fri, 30 Apr 2021 07:11:12 +0800 Message-ID: <20210429231112.GA4951@1b959ea1685b> In-Reply-To: <20210429190926.5086-11-smalin@marvell.com> List-Id: --===============6256344189066564390== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable drivers/nvme/host/tcp-offload.c:106:26: warning: symbol 'nvme_tcp_ofld_look= up_dev' was not declared. Should it be static? Reported-by: kernel test robot Signed-off-by: kernel test robot --- tcp-offload.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/nvme/host/tcp-offload.c b/drivers/nvme/host/tcp-offloa= d.c index aa7cc239abf20..a615007b8c9ab 100644 --- a/drivers/nvme/host/tcp-offload.c +++ b/drivers/nvme/host/tcp-offload.c @@ -103,7 +103,7 @@ void nvme_tcp_ofld_req_done(struct nvme_tcp_ofld_req *r= eq, /* Placeholder - complete request with/without error */ } = -struct nvme_tcp_ofld_dev * +static struct nvme_tcp_ofld_dev * nvme_tcp_ofld_lookup_dev(struct nvme_tcp_ofld_ctrl *ctrl) { struct nvme_tcp_ofld_dev *dev; --===============6256344189066564390==--