From: kernel test robot <lkp@intel.com>
To: Hannes Reinecke <hare@suse.de>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [hare-scsi-devel:tls-netlink.v7 3/20] drivers/nvme/common/keyring.c:14:5: warning: no previous prototype for function 'nvme_keyring_init'
Date: Wed, 22 Mar 2023 02:03:09 +0800 [thread overview]
Message-ID: <202303220128.ky1IoKee-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git tls-netlink.v7
head: 5c13b43fa2c503188a6d668b0dec6a22078329a2
commit: e9b1071a27a0122e041829e87e86852c8b80c04a [3/20] nvme-keyring: register '.nvme' keyring
config: mips-randconfig-r001-20230319 (https://download.01.org/0day-ci/archive/20230322/202303220128.ky1IoKee-lkp@intel.com/config)
compiler: clang version 17.0.0 (https://github.com/llvm/llvm-project 67409911353323ca5edf2049ef0df54132fa1ca7)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install mips cross compiling tool for clang build
# apt-get install binutils-mips-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git/commit/?id=e9b1071a27a0122e041829e87e86852c8b80c04a
git remote add hare-scsi-devel https://git.kernel.org/pub/scm/linux/kernel/git/hare/scsi-devel.git
git fetch --no-tags hare-scsi-devel tls-netlink.v7
git checkout e9b1071a27a0122e041829e87e86852c8b80c04a
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips olddefconfig
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=mips SHELL=/bin/bash drivers/nvme/common/
If you fix the issue, kindly add following tag where applicable
| Reported-by: kernel test robot <lkp@intel.com>
| Link: https://lore.kernel.org/oe-kbuild-all/202303220128.ky1IoKee-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/nvme/common/keyring.c:16:6: warning: unused variable 'err' [-Wunused-variable]
int err;
^
>> drivers/nvme/common/keyring.c:14:5: warning: no previous prototype for function 'nvme_keyring_init' [-Wmissing-prototypes]
int nvme_keyring_init(void)
^
drivers/nvme/common/keyring.c:14:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int nvme_keyring_init(void)
^
static
>> drivers/nvme/common/keyring.c:31:6: warning: no previous prototype for function 'nvme_keyring_exit' [-Wmissing-prototypes]
void nvme_keyring_exit(void)
^
drivers/nvme/common/keyring.c:31:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
void nvme_keyring_exit(void)
^
static
3 warnings generated.
vim +/nvme_keyring_init +14 drivers/nvme/common/keyring.c
13
> 14 int nvme_keyring_init(void)
15 {
16 int err;
17
18 nvme_keyring = keyring_alloc(".nvme",
19 GLOBAL_ROOT_UID, GLOBAL_ROOT_GID,
20 current_cred(),
21 (KEY_POS_ALL & ~KEY_POS_SETATTR) |
22 (KEY_USR_ALL & ~KEY_USR_SETATTR),
23 KEY_ALLOC_NOT_IN_QUOTA, NULL, NULL);
24 if (IS_ERR(nvme_keyring))
25 return PTR_ERR(nvme_keyring);
26
27 return 0;
28 }
29 EXPORT_SYMBOL_GPL(nvme_keyring_init);
30
> 31 void nvme_keyring_exit(void)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests
reply other threads:[~2023-03-21 18:04 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=202303220128.ky1IoKee-lkp@intel.com \
--to=lkp@intel.com \
--cc=hare@suse.de \
--cc=llvm@lists.linux.dev \
--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.