xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: kbuild test robot <lkp@intel.com>
Cc: Juergen Gross <jgross@suse.com>,
	mhocko@suse.com, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, linux-mm@kvack.org, kbuild-all@01.org,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH] mm: don't defer struct page initialization for Xen pv guests
Date: Tue, 20 Feb 2018 15:21:48 -0800	[thread overview]
Message-ID: <20180220152148.2a3ff03d3c8aa6ade8cbae25@linux-foundation.org> (raw)
In-Reply-To: <201802190217.ctfr9bPI%fengguang.wu@intel.com>

On Mon, 19 Feb 2018 02:45:27 +0800 kbuild test robot <lkp@intel.com> wrote:

> [auto build test ERROR on mmotm/master]
> [also build test ERROR on v4.16-rc1 next-20180216]
> [if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
> 
> url:    https://github.com/0day-ci/linux/commits/Juergen-Gross/mm-don-t-defer-struct-page-initialization-for-Xen-pv-guests/20180218-233657
> base:   git://git.cmpxchg.org/linux-mmotm.git master
> config: i386-randconfig-x010-201807 (attached as .config)
> compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
> reproduce:
>         # save the attached .config to linux build tree
>         make ARCH=i386 
> 
> All errors (new ones prefixed by >>):
> 
>    mm/page_alloc.c: In function 'update_defer_init':
> >> mm/page_alloc.c:352:6: error: implicit declaration of function 'xen_pv_domain' [-Werror=implicit-function-declaration]
>      if (xen_pv_domain())
>          ^~~~~~~~~~~~~

I think I already fixed this.



From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-dont-defer-struct-page-initialization-for-xen-pv-guests-fix

explicitly include xen.h

Cc: Juergen Gross <jgross@suse.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---

 mm/page_alloc.c |    1 +
 1 file changed, 1 insertion(+)

diff -puN mm/page_alloc.c~mm-dont-defer-struct-page-initialization-for-xen-pv-guests-fix mm/page_alloc.c
--- a/mm/page_alloc.c~mm-dont-defer-struct-page-initialization-for-xen-pv-guests-fix
+++ a/mm/page_alloc.c
@@ -46,6 +46,7 @@
 #include <linux/stop_machine.h>
 #include <linux/sort.h>
 #include <linux/pfn.h>
+#include <xen/xen.h>
 #include <linux/backing-dev.h>
 #include <linux/fault-inject.h>
 #include <linux/page-isolation.h>
_



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-02-20 23:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20180216133726.30813-1-jgross@suse.com>
2018-02-16 13:59 ` [PATCH] mm: don't defer struct page initialization for Xen pv guests Michal Hocko
     [not found] ` <20180216135940.GQ7275@dhcp22.suse.cz>
2018-02-16 14:02   ` Juergen Gross
     [not found]   ` <1424bb25-7d6a-ee21-83b4-0e90369d6132@suse.com>
2018-02-16 14:21     ` Pavel Tatashin
2018-02-16 14:28     ` Michal Hocko
2018-02-18 18:45 ` kbuild test robot
2018-02-20 23:21   ` Andrew Morton [this message]
2018-02-16 13:37 Juergen Gross

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=20180220152148.2a3ff03d3c8aa6ade8cbae25@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=jgross@suse.com \
    --cc=kbuild-all@01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mhocko@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=xen-devel@lists.xenproject.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).