linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: kbuild-all@01.org, Andrew Morton <akpm@linux-foundation.org>,
	Vlastimil Babka <vbabka@suse.cz>, Mel Gorman <mgorman@suse.de>,
	mhocko@suse.com, js1304@gmail.com,
	Johannes Weiner <hannes@cmpxchg.org>,
	alexander.h.duyck@redhat.com, zhongjiang@huawei.com,
	Linux MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: reset migratetype if the range spans two pageblocks
Date: Fri, 16 Oct 2015 18:59:57 +0800	[thread overview]
Message-ID: <201510161801.SLot2IHE%fengguang.wu@intel.com> (raw)
In-Reply-To: <5620CC36.4090107@huawei.com>

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

Hi Xishi,

[auto build test ERROR on v4.3-rc5 -- if it's inappropriate base, please suggest rules for selecting the more suitable base]

url:    https://github.com/0day-ci/linux/commits/Xishi-Qiu/mm-reset-migratetype-if-the-range-spans-two-pageblocks/20151016-180949
config: i386-randconfig-s1-201541 (attached as .config)
reproduce:
        # save the attached .config to linux build tree
        make ARCH=i386 

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

   mm/page_alloc.c: In function '__free_one_page':
>> mm/page_alloc.c:731:3: error: implicit declaration of function 'change_pageblock_range' [-Werror=implicit-function-declaration]
      change_pageblock_range(page, order, migratetype);
      ^
   mm/page_alloc.c: At top level:
>> mm/page_alloc.c:1515:13: warning: conflicting types for 'change_pageblock_range'
    static void change_pageblock_range(struct page *pageblock_page,
                ^
>> mm/page_alloc.c:1515:13: error: static declaration of 'change_pageblock_range' follows non-static declaration
   mm/page_alloc.c:731:3: note: previous implicit declaration of 'change_pageblock_range' was here
      change_pageblock_range(page, order, migratetype);
      ^
   cc1: some warnings being treated as errors

vim +/change_pageblock_range +731 mm/page_alloc.c

   725	
   726		list_add(&page->lru, &zone->free_area[order].free_list[migratetype]);
   727	out:
   728		zone->free_area[order].nr_free++;
   729		/* If the range spans two pageblocks, reset the migratetype. */
   730		if (order > pageblock_order)
 > 731			change_pageblock_range(page, order, migratetype);
   732	}
   733	
   734	static inline int free_pages_check(struct page *page)

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

  parent reply	other threads:[~2015-10-16 11:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16 10:06 Xishi Qiu
2015-10-16 10:12 ` Xishi Qiu
2015-10-16 10:59 ` kbuild test robot [this message]
2015-10-16 11:59 ` Vlastimil Babka

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=201510161801.SLot2IHE%fengguang.wu@intel.com \
    --to=lkp@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@redhat.com \
    --cc=hannes@cmpxchg.org \
    --cc=js1304@gmail.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=qiuxishi@huawei.com \
    --cc=vbabka@suse.cz \
    --cc=zhongjiang@huawei.com \
    /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