From: kernel test robot <lkp@intel.com>
To: Roberto Sassu <roberto.sassu@huawei.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [robertosassu:ima-evm-lsms-v4-devel-v10 22/26] security/integrity/ima/ima_main.c:1156:12: warning: no previous prototype for 'dummy_init_ima_lsm'
Date: Fri, 27 Oct 2023 07:13:10 +0800 [thread overview]
Message-ID: <202310270736.GCuPmFaZ-lkp@intel.com> (raw)
tree: https://github.com/robertosassu/linux ima-evm-lsms-v4-devel-v10
head: b56de9fb8f4f26ea450fa3e533685d61089d559a
commit: f08ce9726b1afbfa835cf9599d772636f8dada1c [22/26] ima: Move to LSM infrastructure
config: alpha-allyesconfig (https://download.01.org/0day-ci/archive/20231027/202310270736.GCuPmFaZ-lkp@intel.com/config)
compiler: alpha-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231027/202310270736.GCuPmFaZ-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/202310270736.GCuPmFaZ-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> security/integrity/ima/ima_main.c:1156:12: warning: no previous prototype for 'dummy_init_ima_lsm' [-Wmissing-prototypes]
1156 | int __init dummy_init_ima_lsm(void)
| ^~~~~~~~~~~~~~~~~~
vim +/dummy_init_ima_lsm +1156 security/integrity/ima/ima_main.c
1154
1155 /* Introduce a dummy function as 'ima' init function (it cannot be NULL). */
> 1156 int __init dummy_init_ima_lsm(void)
1157 {
1158 return 0;
1159 }
1160
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-26 23:13 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=202310270736.GCuPmFaZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=roberto.sassu@huawei.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 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.