All of lore.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [tglx-devel:x86/tlb 7/15] arch/x86/mm/tlb.c:27:37: error: implicit declaration of function 'native_flush_tlb_one_user'; did you mean 'native_flush_tlb_others'?
Date: Mon, 20 Apr 2020 20:53:48 +0800	[thread overview]
Message-ID: <202004202043.GT11TPNe%lkp@intel.com> (raw)

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

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/tlb
head:   b458a5f2cee720aa4fd51f492f28a2d6cf112195
commit: 8c21942ff30bf37034e0fd04e93c5ee7e8f54357 [7/15] x86/tlb: Move __flush_tlb_one_user() out of line
config: x86_64-defconfig (attached as .config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce:
        git checkout 8c21942ff30bf37034e0fd04e93c5ee7e8f54357
        # save the attached .config to linux build tree
        make ARCH=x86_64 

If you fix the issue, kindly add following tag as appropriate
Reported-by: kbuild test robot <lkp@intel.com>

All errors (new ones prefixed by >>):

   arch/x86/mm/tlb.c: In function 'flush_tlb_func_common':
>> arch/x86/mm/tlb.c:27:37: error: implicit declaration of function 'native_flush_tlb_one_user'; did you mean 'native_flush_tlb_others'? [-Werror=implicit-function-declaration]
    # define __flush_tlb_one_user(addr) native_flush_tlb_one_user(addr)
                                        ^
   arch/x86/mm/tlb.c:675:4: note: in expansion of macro '__flush_tlb_one_user'
       __flush_tlb_one_user(addr);
       ^~~~~~~~~~~~~~~~~~~~
   arch/x86/mm/tlb.c: At top level:
   arch/x86/mm/tlb.c:924:18: warning: conflicting types for 'native_flush_tlb_one_user'
    STATIC_NOPV void native_flush_tlb_one_user(unsigned long addr)
                     ^~~~~~~~~~~~~~~~~~~~~~~~~
>> arch/x86/mm/tlb.c:924:18: error: static declaration of 'native_flush_tlb_one_user' follows non-static declaration
   arch/x86/mm/tlb.c:27:37: note: previous implicit declaration of 'native_flush_tlb_one_user' was here
    # define __flush_tlb_one_user(addr) native_flush_tlb_one_user(addr)
                                        ^
   arch/x86/mm/tlb.c:675:4: note: in expansion of macro '__flush_tlb_one_user'
       __flush_tlb_one_user(addr);
       ^~~~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +27 arch/x86/mm/tlb.c

    20	
    21	#ifdef CONFIG_PARAVIRT
    22	# define STATIC_NOPV
    23	#else
    24	# define STATIC_NOPV			static
    25	# define __flush_tlb_local		native_flush_tlb_local
    26	# define __flush_tlb_global		native_flush_tlb_global
  > 27	# define __flush_tlb_one_user(addr)	native_flush_tlb_one_user(addr)
    28	#endif
    29	

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org

[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 35484 bytes --]

             reply	other threads:[~2020-04-20 12:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-20 12:53 kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-04-20 14:56 [tglx-devel:x86/tlb 7/15] arch/x86/mm/tlb.c:27:37: error: implicit declaration of function 'native_flush_tlb_one_user'; did you mean 'native_flush_tlb_others'? kbuild test robot

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=202004202043.GT11TPNe%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=kbuild-all@lists.01.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.