From: kbuild test robot <lkp@intel.com>
Cc: Juergen Gross <jgross@suse.com>,
Stefano Stabellini <sstabellini@kernel.org>,
linux-kernel@vger.kernel.org, kbuild-all@01.org,
xen-devel@lists.xenproject.org,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Roger Pau Monne <roger.pau@citrix.com>
Subject: Re: [PATCH v2 3/3] xen: share start flags between PV and PVH
Date: Thu, 10 May 2018 00:34:57 +0800 [thread overview]
Message-ID: <201805092234.YH6cRkhb%fengguang.wu__22363.8177187697$1525883648$gmane$org@intel.com> (raw)
In-Reply-To: <20180509102129.14832-4-roger.pau@citrix.com>
[-- Attachment #1: Type: text/plain, Size: 1779 bytes --]
Hi Roger,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.17-rc4 next-20180509]
[cannot apply to xen-tip/linux-next]
[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/Roger-Pau-Monne/xen-pvh-Dom0-support/20180509-222240
config: x86_64-randconfig-x009-201818 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-16) 7.3.0
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
arch/x86/xen/enlighten_pvh.c: In function 'xen_prepare_pvh':
>> arch/x86/xen/enlighten_pvh.c:101:2: error: 'xen_start_flags' undeclared (first use in this function); did you mean 'xen_start_info'?
xen_start_flags = pvh_start_info.flags;
^~~~~~~~~~~~~~~
xen_start_info
arch/x86/xen/enlighten_pvh.c:101:2: note: each undeclared identifier is reported only once for each function it appears in
vim +101 arch/x86/xen/enlighten_pvh.c
84
85 /*
86 * This routine (and those that it might call) should not use
87 * anything that lives in .bss since that segment will be cleared later.
88 */
89 void __init xen_prepare_pvh(void)
90 {
91 u32 msr;
92 u64 pfn;
93
94 if (pvh_start_info.magic != XEN_HVM_START_MAGIC_VALUE) {
95 xen_raw_printk("Error: Unexpected magic value (0x%08x)\n",
96 pvh_start_info.magic);
97 BUG();
98 }
99
100 xen_pvh = 1;
> 101 xen_start_flags = pvh_start_info.flags;
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 29793 bytes --]
[-- Attachment #3: Type: text/plain, Size: 157 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-05-09 16:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-09 10:21 [PATCH v2 0/3] xen/pvh: Dom0 support Roger Pau Monne
2018-05-09 10:21 ` [PATCH v2 1/3] xen/pvh: enable and set default MTRR type Roger Pau Monne
2018-05-09 10:21 ` Roger Pau Monne
2018-05-09 10:56 ` [Xen-devel] " Andrew Cooper
2018-05-09 11:30 ` Roger Pau Monné
2018-05-09 15:11 ` Roger Pau Monné
2018-05-10 11:52 ` Wei Liu
2018-05-10 11:52 ` Wei Liu
2018-05-11 7:33 ` Juergen Gross
2018-05-11 7:33 ` [Xen-devel] " Juergen Gross
2018-05-09 15:11 ` Roger Pau Monné
2018-05-09 11:30 ` Roger Pau Monné
2018-05-09 10:56 ` Andrew Cooper
2018-05-09 10:21 ` [PATCH v2 2/3] xen/store: do not store local values in xen_start_info Roger Pau Monne
2018-05-09 10:21 ` Roger Pau Monne
2018-05-11 7:34 ` Juergen Gross
2018-05-11 7:34 ` Juergen Gross
2018-05-17 6:43 ` Juergen Gross
2018-05-17 6:43 ` Juergen Gross
2018-05-09 10:21 ` [PATCH v2 3/3] xen: share start flags between PV and PVH Roger Pau Monne
2018-05-09 10:21 ` Roger Pau Monne
2018-05-09 16:34 ` kbuild test robot
2018-05-09 16:34 ` kbuild test robot [this message]
2018-05-09 21:47 ` Stefano Stabellini
2018-05-09 21:47 ` Stefano Stabellini
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='201805092234.YH6cRkhb%fengguang.wu__22363.8177187697$1525883648$gmane$org@intel.com' \
--to=lkp@intel.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jgross@suse.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roger.pau@citrix.com \
--cc=sstabellini@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 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.