linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Michael Kelley <mikelley@microsoft.com>
Cc: kbuild-all@lists.01.org,
	Linux Memory Management List <linux-mm@kvack.org>,
	Wei Liu <wei.liu@kernel.org>
Subject: [linux-next:master 2651/2892] arch/x86/kernel/cpu/mshyperv.c:94:6: warning: no previous prototype for 'hv_setup_stimer0_handler'
Date: Wed, 10 Mar 2021 00:54:43 +0800	[thread overview]
Message-ID: <202103100037.ZADnf6oz-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2455 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   3aa6f5082286ec74926f3587b05697ba2fd0ace7
commit: ec866be6ec547c9e1cc4451f04250e08b5fe67c7 [2651/2892] clocksource/drivers/hyper-v: Move handling of STIMER0 interrupts
config: i386-randconfig-r031-20210309 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=ec866be6ec547c9e1cc4451f04250e08b5fe67c7
        git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
        git fetch --no-tags linux-next master
        git checkout ec866be6ec547c9e1cc4451f04250e08b5fe67c7
        # save the attached .config to linux build tree
        make W=1 ARCH=i386 

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/kernel/cpu/mshyperv.c:94:6: warning: no previous prototype for 'hv_setup_stimer0_handler' [-Wmissing-prototypes]
      94 | void hv_setup_stimer0_handler(void (*handler)(void))
         |      ^~~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/kernel/cpu/mshyperv.c:99:6: warning: no previous prototype for 'hv_remove_stimer0_handler' [-Wmissing-prototypes]
      99 | void hv_remove_stimer0_handler(void)
         |      ^~~~~~~~~~~~~~~~~~~~~~~~~
--
>> drivers/clocksource/hyperv_timer.c:190:13: warning: no previous prototype for 'hv_setup_stimer0_handler' [-Wmissing-prototypes]
     190 | void __weak hv_setup_stimer0_handler(void (*handler)(void))
         |             ^~~~~~~~~~~~~~~~~~~~~~~~
>> drivers/clocksource/hyperv_timer.c:194:13: warning: no previous prototype for 'hv_remove_stimer0_handler' [-Wmissing-prototypes]
     194 | void __weak hv_remove_stimer0_handler(void)
         |             ^~~~~~~~~~~~~~~~~~~~~~~~~


vim +/hv_setup_stimer0_handler +94 arch/x86/kernel/cpu/mshyperv.c

    92	
    93	/* For x86/x64, override weak placeholders in hyperv_timer.c */
  > 94	void hv_setup_stimer0_handler(void (*handler)(void))
    95	{
    96		hv_stimer0_handler = handler;
    97	}
    98	
  > 99	void hv_remove_stimer0_handler(void)
   100	{
   101		/* We have no way to deallocate the interrupt gate */
   102		hv_stimer0_handler = NULL;
   103	}
   104	

---
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: 29329 bytes --]

                 reply	other threads:[~2021-03-09 16:56 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=202103100037.ZADnf6oz-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=mikelley@microsoft.com \
    --cc=wei.liu@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