From: kernel test robot <yujie.liu@intel.com>
To: Saurabh Sengar <ssengar@linux.microsoft.com>, <kys@microsoft.com>,
<haiyangz@microsoft.com>, <wei.liu@kernel.org>,
<decui@microsoft.com>, <tglx@linutronix.de>, <mingo@redhat.com>,
<bp@alien8.de>, <dave.hansen@linux.intel.com>, <x86@kernel.org>,
<hpa@zytor.com>, <linux-hyperv@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <mikelley@microsoft.com>
Cc: <oe-kbuild-all@lists.linux.dev>, <minipli@grsecurity.net>,
<ssengar@microsoft.com>
Subject: Re: [PATCH] x86/hyperv: Remove hv_vtl_early_init initcall
Date: Thu, 28 Sep 2023 09:36:34 +0800 [thread overview]
Message-ID: <202309201327.J4pfXnUv-lkp@intel.com> (raw)
In-Reply-To: <1695185552-19910-1-git-send-email-ssengar@linux.microsoft.com>
Hi Saurabh,
kernel test robot noticed the following build warnings:
[auto build test WARNING on v6.6-rc2]
[also build test WARNING on linus/master next-20230920]
[cannot apply to tip/x86/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Saurabh-Sengar/x86-hyperv-Remove-hv_vtl_early_init-initcall/20230920-125357
base: v6.6-rc2
patch link: https://lore.kernel.org/r/1695185552-19910-1-git-send-email-ssengar%40linux.microsoft.com
patch subject: [PATCH] x86/hyperv: Remove hv_vtl_early_init initcall
config: i386-tinyconfig (https://download.01.org/0day-ci/archive/20230920/202309201327.J4pfXnUv-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/20230920/202309201327.J4pfXnUv-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 <yujie.liu@intel.com>
| Closes: https://lore.kernel.org/r/202309201327.J4pfXnUv-lkp@intel.com/
All warnings (new ones prefixed by >>):
In file included from arch/x86/mm/pat/set_memory.c:36:
arch/x86/include/asm/mshyperv.h: In function 'hv_vtl_early_init':
arch/x86/include/asm/mshyperv.h:346:1: error: no return statement in function returning non-void [-Werror=return-type]
346 | static int __init hv_vtl_early_init(void) {}
| ^~~~~~
arch/x86/include/asm/mshyperv.h: At top level:
>> arch/x86/include/asm/mshyperv.h:346:19: warning: 'hv_vtl_early_init' defined but not used [-Wunused-function]
346 | static int __init hv_vtl_early_init(void) {}
| ^~~~~~~~~~~~~~~~~
cc1: some warnings being treated as errors
vim +/hv_vtl_early_init +346 arch/x86/include/asm/mshyperv.h
79cadff2d92bb8 Vitaly Kuznetsov 2017-08-02 339
765e33f5211ab6 Michael Kelley 2019-05-30 340
3be1bc2fe9d2e4 Saurabh Sengar 2023-04-10 341 #ifdef CONFIG_HYPERV_VTL_MODE
3be1bc2fe9d2e4 Saurabh Sengar 2023-04-10 342 void __init hv_vtl_init_platform(void);
9081cfc5d0e7fa Saurabh Sengar 2023-09-19 343 int __init hv_vtl_early_init(void);
3be1bc2fe9d2e4 Saurabh Sengar 2023-04-10 344 #else
3be1bc2fe9d2e4 Saurabh Sengar 2023-04-10 345 static inline void __init hv_vtl_init_platform(void) {}
9081cfc5d0e7fa Saurabh Sengar 2023-09-19 @346 static int __init hv_vtl_early_init(void) {}
3be1bc2fe9d2e4 Saurabh Sengar 2023-04-10 347 #endif
3be1bc2fe9d2e4 Saurabh Sengar 2023-04-10 348
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2023-09-28 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-20 4:52 [PATCH] x86/hyperv: Remove hv_vtl_early_init initcall Saurabh Sengar
2023-09-21 7:17 ` Mathias Krause
2023-09-21 17:14 ` Saurabh Singh Sengar
2023-09-21 18:27 ` Mathias Krause
2023-09-22 3:45 ` Saurabh Singh Sengar
2023-09-28 1:36 ` kernel test robot [this message]
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=202309201327.J4pfXnUv-lkp@intel.com \
--to=yujie.liu@intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikelley@microsoft.com \
--cc=mingo@redhat.com \
--cc=minipli@grsecurity.net \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ssengar@linux.microsoft.com \
--cc=ssengar@microsoft.com \
--cc=tglx@linutronix.de \
--cc=wei.liu@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).