From: kernel test robot <lkp@intel.com>
To: zhenwei pi <pizhenwei@bytedance.com>,
mst@redhat.com, arei.gonglei@huawei.com
Cc: kbuild-all@lists.01.org, jasowang@redhat.com,
virtualization@lists.linux-foundation.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org,
helei.sig11@bytedance.com, zhenwei pi <pizhenwei@bytedance.com>
Subject: [RFC PATCH] virtio-crypto: virtio_crypto_rsa_do_req() can be static
Date: Fri, 21 Jan 2022 16:29:52 +0800 [thread overview]
Message-ID: <20220121082951.GA46247@b53fa9759326> (raw)
In-Reply-To: <20220121022438.1042547-4-pizhenwei@bytedance.com>
drivers/crypto/virtio/virtio_crypto_akcipher_algo.c:276:5: warning: symbol 'virtio_crypto_rsa_do_req' was not declared. Should it be static?
Reported-by: kernel test robot <lkp@intel.com>
Signed-off-by: kernel test robot <lkp@intel.com>
---
virtio_crypto_akcipher_algo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/crypto/virtio/virtio_crypto_akcipher_algo.c b/drivers/crypto/virtio/virtio_crypto_akcipher_algo.c
index eebccf71b2fab..2b3f8780b7551 100644
--- a/drivers/crypto/virtio/virtio_crypto_akcipher_algo.c
+++ b/drivers/crypto/virtio/virtio_crypto_akcipher_algo.c
@@ -273,7 +273,7 @@ static int __virtio_crypto_akcipher_do_req(struct virtio_crypto_akcipher_request
return -ENOMEM;
}
-int virtio_crypto_rsa_do_req(struct crypto_engine *engine, void *vreq)
+static int virtio_crypto_rsa_do_req(struct crypto_engine *engine, void *vreq)
{
struct akcipher_request *req = container_of(vreq, struct akcipher_request, base);
struct virtio_crypto_akcipher_request *vc_akcipher_req = akcipher_request_ctx(req);
next prev parent reply other threads:[~2022-01-21 8:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 2:24 [PATCH 0/3] Introduce akcipher service for virtio-crypto zhenwei pi
2022-01-21 2:24 ` [PATCH 1/3] virtio_crypto: Introduce VIRTIO_CRYPTO_NOSPC zhenwei pi
2022-02-10 7:22 ` Gonglei (Arei)
2022-01-21 2:24 ` [PATCH 2/3] virtio-crypto: introduce akcipher service zhenwei pi
2022-02-10 7:51 ` Gonglei (Arei)
2022-02-10 8:18 ` zhenwei pi
2022-02-10 9:21 ` Gonglei (Arei)
2022-01-21 2:24 ` [PATCH 3/3] virtio-crypto: implement RSA algorithm zhenwei pi
2022-01-21 6:36 ` kernel test robot
2022-01-21 8:29 ` kernel test robot [this message]
2022-01-21 8:39 ` kernel test robot
2022-01-21 21:43 ` kernel test robot
2022-01-22 0:19 ` kernel test robot
2022-02-10 6:55 ` PING: [PATCH 0/3] Introduce akcipher service for virtio-crypto zhenwei pi
2022-02-10 7:17 ` Jason Wang
2022-02-10 7:23 ` Michael S. Tsirkin
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=20220121082951.GA46247@b53fa9759326 \
--to=lkp@intel.com \
--cc=arei.gonglei@huawei.com \
--cc=helei.sig11@bytedance.com \
--cc=jasowang@redhat.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pizhenwei@bytedance.com \
--cc=virtualization@lists.linux-foundation.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