From: kernel test robot <lkp@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [peterz-queue:x86/core 12/14] arch/x86/hyperv/ivm.c:395:60: warning: control reaches end of non-void function
Date: Wed, 30 Apr 2025 19:16:30 +0800 [thread overview]
Message-ID: <202504301906.aofQDfxo-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: i386-allmodconfig (https://download.01.org/0day-ci/archive/20250430/202504301906.aofQDfxo-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/20250430/202504301906.aofQDfxo-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/202504301906.aofQDfxo-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/x86/hyperv/ivm.c: In function 'hv_snp_hypercall':
>> arch/x86/hyperv/ivm.c:395:60: warning: control reaches end of non-void function [-Wreturn-type]
395 | u64 hv_snp_hypercall(u64 control, u64 param1, u64 param2) {}
| ^
arch/x86/hyperv/ivm.c: In function 'hv_tdx_hypercall':
arch/x86/hyperv/ivm.c:445:60: warning: control reaches end of non-void function [-Wreturn-type]
445 | u64 hv_tdx_hypercall(u64 control, u64 param1, u64 param2) {}
| ^
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-30 11:17 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=202504301906.aofQDfxo-lkp@intel.com \
--to=lkp@intel.com \
--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 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.