From: kernel test robot <lkp@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>
Cc: kbuild-all@01.org, clang-built-linux@googlegroups.com,
linux-kernel@vger.kernel.org, x86@kernel.org,
Borislav Petkov <bp@suse.de>
Subject: [tip:x86/seves 2/2] arch/x86/mm/mem_encrypt.c:487:5: warning: no previous prototype for function 'arch_has_restricted_virtio_memory_access'
Date: Mon, 8 Mar 2021 22:36:58 +0800 [thread overview]
Message-ID: <202103082256.RQQzWxAT-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2010 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/seves
head: 9da54be651f8a856d9e6c14183d0df948e222103
commit: 9da54be651f8a856d9e6c14183d0df948e222103 [2/2] x86/virtio: Have SEV guests enforce restricted virtio memory access
config: x86_64-randconfig-a013-20210308 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 3a11a41795bec548e91621caaa4cc00fc31b2212)
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 x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=9da54be651f8a856d9e6c14183d0df948e222103
git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
git fetch --no-tags tip x86/seves
git checkout 9da54be651f8a856d9e6c14183d0df948e222103
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/mm/mem_encrypt.c:487:5: warning: no previous prototype for function 'arch_has_restricted_virtio_memory_access' [-Wmissing-prototypes]
int arch_has_restricted_virtio_memory_access(void)
^
arch/x86/mm/mem_encrypt.c:487:1: note: declare 'static' if the function is not intended to be used outside of this translation unit
int arch_has_restricted_virtio_memory_access(void)
^
static
1 warning generated.
vim +/arch_has_restricted_virtio_memory_access +487 arch/x86/mm/mem_encrypt.c
486
> 487 int arch_has_restricted_virtio_memory_access(void)
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 39278 bytes --]
reply other threads:[~2021-03-08 14:38 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=202103082256.RQQzWxAT-lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@suse.de \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®