From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: [peterz-queue:x86/core 12/14] arch/x86/hyperv/ivm.c:395:60: warning: non-void function does not return a value
Date: Wed, 30 Apr 2025 04:48:45 +0800 [thread overview]
Message-ID: <202504300410.yCsLT0DE-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git x86/core
head: a4f560f88ebe36d504463b63e648dbf3468f836c
commit: 34c83ece500350809581ca9365b38908a8973471 [12/14] x86,hyperv: Clean up hv_do_hypercall()
config: x86_64-buildonly-randconfig-002-20250430 (https://download.01.org/0day-ci/archive/20250430/202504300410.yCsLT0DE-lkp@intel.com/config)
compiler: clang version 20.1.2 (https://github.com/llvm/llvm-project 58df0ef89dd64126512e4ee27b4ac3fd8ddf6247)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250430/202504300410.yCsLT0DE-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/202504300410.yCsLT0DE-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> arch/x86/hyperv/ivm.c:395:60: warning: non-void function does not return a value [-Wreturn-type]
395 | u64 hv_snp_hypercall(u64 control, u64 param1, u64 param2) {}
| ^
arch/x86/hyperv/ivm.c:445:60: warning: non-void function does not return a value [-Wreturn-type]
445 | u64 hv_tdx_hypercall(u64 control, u64 param1, u64 param2) {}
| ^
arch/x86/hyperv/ivm.c:393:20: warning: unused function 'hv_ghcb_msr_write' [-Wunused-function]
393 | static inline void hv_ghcb_msr_write(u64 msr, u64 value) {}
| ^~~~~~~~~~~~~~~~~
arch/x86/hyperv/ivm.c:394:20: warning: unused function 'hv_ghcb_msr_read' [-Wunused-function]
394 | static inline void hv_ghcb_msr_read(u64 msr, u64 *value) {}
| ^~~~~~~~~~~~~~~~
arch/x86/hyperv/ivm.c:443:20: warning: unused function 'hv_tdx_msr_write' [-Wunused-function]
443 | static inline void hv_tdx_msr_write(u64 msr, u64 value) {}
| ^~~~~~~~~~~~~~~~
arch/x86/hyperv/ivm.c:444:20: warning: unused function 'hv_tdx_msr_read' [-Wunused-function]
444 | static inline void hv_tdx_msr_read(u64 msr, u64 *value) {}
| ^~~~~~~~~~~~~~~
6 warnings generated.
vim +395 arch/x86/hyperv/ivm.c
391
392 #else
393 static inline void hv_ghcb_msr_write(u64 msr, u64 value) {}
394 static inline void hv_ghcb_msr_read(u64 msr, u64 *value) {}
> 395 u64 hv_snp_hypercall(u64 control, u64 param1, u64 param2) {}
396 #endif /* CONFIG_AMD_MEM_ENCRYPT */
397
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-04-29 20:49 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=202504300410.yCsLT0DE-lkp@intel.com \
--to=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.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