From: kbuild test robot <lkp@intel.com>
To: tip-bot2 for Thomas Hellstrom <tip-bot2@linutronix.de>
Cc: kbuild-all@01.org, linux-tip-commits@vger.kernel.org,
Thomas Hellstrom <thellstrom@vmware.com>,
Borislav Petkov <bp@suse.de>, Doug Covelli <dcovelli@vmware.com>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
linux-input@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
VMware Graphics <linux-graphics-maintainer@vmware.com>,
pv-drivers@vmware.com, x86-ml <x86@kernel.org>,
Ingo Molnar <mingo@kernel.org>, Borislav Petkov <bp@alien8.de>,
linux-kernel@vger.kernel.org
Subject: Re: [tip: x86/vmware] input/vmmouse: Update the backdoor call with support for new instructions
Date: Fri, 30 Aug 2019 00:01:48 +0800 [thread overview]
Message-ID: <201908292325.aLXyyzEx%lkp@intel.com> (raw)
In-Reply-To: <156699905611.5321.15444519862547054670.tip-bot2@tip-bot2>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Hi tip-bot2,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[cannot apply to v5.3-rc6 next-20190829]
[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/tip-bot2-for-Thomas-Hellstrom/input-vmmouse-Update-the-backdoor-call-with-support-for-new-instructions/20190829-205315
config: x86_64-randconfig-s0-08291619 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.2-10+deb8u1) 4.9.2
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/input/mouse/vmmouse.c:19:24: fatal error: asm/vmware.h: No such file or directory
#include <asm/vmware.h>
^
compilation terminated.
vim +19 drivers/input/mouse/vmmouse.c
> 19 #include <asm/vmware.h>
20
---
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: 33097 bytes --]
next prev parent reply other threads:[~2019-08-29 16:02 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 8:03 [PATCH v3 0/4] Add support for updated vmware hypercall instruction Thomas Hellström (VMware)
2019-08-28 8:03 ` [PATCH v3 1/4] x86/vmware: Update platform detection code for VMCALL/VMMCALL hypercalls Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-28 8:03 ` [PATCH v3 2/4] x86/vmware: Add a header file for hypercall definitions Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-28 8:03 ` [PATCH v3 3/4] drm/vmwgfx: Update the backdoor call with support for new instructions Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-28 8:03 ` [PATCH v3 4/4] input/vmmouse: " Thomas Hellström (VMware)
2019-08-28 13:30 ` [tip: x86/vmware] " tip-bot2 for Thomas Hellstrom
2019-08-29 16:01 ` kbuild test robot [this message]
2019-08-29 16:33 ` Borislav Petkov
2019-08-30 1:03 ` [kbuild-all] " Philip Li
2019-08-30 6:06 ` Thomas Gleixner
2019-08-30 6:20 ` Philip Li
2019-08-30 6:33 ` Philip Li
2019-08-30 7:58 ` Thomas Gleixner
2019-08-30 8:06 ` Borislav Petkov
2019-08-30 14:36 ` Philip Li
2019-08-30 14:46 ` Borislav Petkov
2019-08-30 15:00 ` Philip Li
2019-08-30 15:06 ` Borislav Petkov
2019-08-30 15:26 ` Philip Li
2019-08-30 15:08 ` Philip Li
2019-08-30 19:35 ` Borislav Petkov
2019-09-02 1:13 ` Philip Li
2019-09-02 9:36 ` Borislav Petkov
2019-09-03 1:06 ` Philip Li
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=201908292325.aLXyyzEx%lkp@intel.com \
--to=lkp@intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=dcovelli@vmware.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hpa@zytor.com \
--cc=kbuild-all@01.org \
--cc=linux-graphics-maintainer@vmware.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=pv-drivers@vmware.com \
--cc=tglx@linutronix.de \
--cc=thellstrom@vmware.com \
--cc=tip-bot2@linutronix.de \
--cc=x86@kernel.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).