From: kernel test robot <lkp@intel.com>
To: kernel@openeuler.org
Cc: oe-kbuild-all@lists.linux.dev
Subject: [openeuler:OLK-6.6 2331/2331] drivers/crypto/ccp/hygon/vpsp.c:588:10: sparse: sparse: symbol 'allow_default_vid' was not declared. Should it be static?
Date: Thu, 29 May 2025 17:01:23 +0800 [thread overview]
Message-ID: <202505291615.pbSUmoIC-lkp@intel.com> (raw)
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: d6c09e6ce9d7651c2136ae254cbc3c9845fd0317
commit: e2861aaa47961017ada7f66de11104bbf3b85eb1 [2331/2331] crypto: ccp: move vpsp-related functions to vpsp.c
config: x86_64-randconfig-121-20250529 (https://download.01.org/0day-ci/archive/20250529/202505291615.pbSUmoIC-lkp@intel.com/config)
compiler: gcc-12 (Debian 12.2.0-14) 12.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250529/202505291615.pbSUmoIC-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202505291615.pbSUmoIC-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
drivers/crypto/ccp/hygon/vpsp.c:72:1: sparse: sparse: symbol 'g_hbuf_wrap' was not declared. Should it be static?
drivers/crypto/ccp/hygon/vpsp.c:559:1: sparse: sparse: symbol 'vpsp_rwlock' was not declared. Should it be static?
>> drivers/crypto/ccp/hygon/vpsp.c:588:10: sparse: sparse: symbol 'allow_default_vid' was not declared. Should it be static?
>> drivers/crypto/ccp/hygon/vpsp.c:589:6: sparse: sparse: symbol 'vpsp_set_default_vid_permission' was not declared. Should it be static?
vim +/allow_default_vid +588 drivers/crypto/ccp/hygon/vpsp.c
582
583 /**
584 * When 'allow_default_vid' is set to 1,
585 * QEMU is allowed to use 'vid 0' by default
586 * in the absence of a valid 'vid' setting.
587 */
> 588 uint32_t allow_default_vid = 1;
> 589 void vpsp_set_default_vid_permission(uint32_t is_allow)
590 {
591 allow_default_vid = is_allow;
592 }
593
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-29 9:01 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202505291615.pbSUmoIC-lkp@intel.com \
--to=lkp@intel.com \
--cc=kernel@openeuler.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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.