linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <fengguang.wu@intel.com>
Cc: kbuild-all@01.org, Johannes Weiner <hannes@cmpxchg.org>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Linux Memory Management List <linux-mm@kvack.org>
Subject: [mmotm:master 86/178] include/asm-generic/tlb.h:133:3: error: implicit declaration of function '__tlb_adjust_range'
Date: Sat, 4 Jun 2016 08:55:10 +0800	[thread overview]
Message-ID: <201606040808.POQy02Tx%fengguang.wu@intel.com> (raw)

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

tree:   git://git.cmpxchg.org/linux-mmotm.git master
head:   2e0066ec9585a5074c8040d639c3c669eb4e905f
commit: d219cbe49c1d86c9ff2be25d9238047e878295b1 [86/178] mm: change the interface for __tlb_remove_page()
config: i386-tinyconfig (attached as .config)
compiler: gcc-6 (Debian 6.1.1-1) 6.1.1 20160430
reproduce:
        git checkout d219cbe49c1d86c9ff2be25d9238047e878295b1
        # save the attached .config to linux build tree
        make ARCH=i386 

Note: the mmotm/master HEAD 2e0066ec9585a5074c8040d639c3c669eb4e905f builds fine.
      It only hurts bisectibility.

All error/warnings (new ones prefixed by >>):

   In file included from arch/x86/include/asm/tlb.h:16:0,
                    from arch/x86/include/asm/efi.h:7,
                    from arch/x86/kernel/setup.c:81:
   include/asm-generic/tlb.h: In function 'tlb_remove_page':
>> include/asm-generic/tlb.h:133:3: error: implicit declaration of function '__tlb_adjust_range' [-Werror=implicit-function-declaration]
      __tlb_adjust_range(tlb, tlb->addr);
      ^~~~~~~~~~~~~~~~~~
   include/asm-generic/tlb.h: At top level:
>> include/asm-generic/tlb.h:138:20: warning: conflicting types for '__tlb_adjust_range'
    static inline void __tlb_adjust_range(struct mmu_gather *tlb,
                       ^~~~~~~~~~~~~~~~~~
>> include/asm-generic/tlb.h:138:20: error: static declaration of '__tlb_adjust_range' follows non-static declaration
   include/asm-generic/tlb.h:133:3: note: previous implicit declaration of '__tlb_adjust_range' was here
      __tlb_adjust_range(tlb, tlb->addr);
      ^~~~~~~~~~~~~~~~~~
   cc1: some warnings being treated as errors

vim +/__tlb_adjust_range +133 include/asm-generic/tlb.h

   127	 *	required.
   128	 */
   129	static inline void tlb_remove_page(struct mmu_gather *tlb, struct page *page)
   130	{
   131		if (__tlb_remove_page(tlb, page)) {
   132			tlb_flush_mmu(tlb);
 > 133			__tlb_adjust_range(tlb, tlb->addr);
   134			__tlb_remove_page(tlb, page);
   135		}
   136	}
   137	
 > 138	static inline void __tlb_adjust_range(struct mmu_gather *tlb,
   139					      unsigned long address)
   140	{
   141		tlb->start = min(tlb->start, address);

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 6341 bytes --]

                 reply	other threads:[~2016-06-04  1:09 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=201606040808.POQy02Tx%fengguang.wu@intel.com \
    --to=fengguang.wu@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=hannes@cmpxchg.org \
    --cc=kbuild-all@01.org \
    --cc=linux-mm@kvack.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