From: kbuild test robot <lkp@intel.com>
To: mikelley@exchange.microsoft.com
Cc: kbuild-all@01.org, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, devel@linuxdriverproject.org,
olaf@aepfle.de, apw@canonical.com, vkuznets@redhat.com,
jasowang@redhat.com, leann.ogasawara@canonical.com,
marcelo.cerri@canonical.com, sthemmin@microsoft.com,
kys@microsoft.com, Michael Kelley <mikelley@microsoft.com>
Subject: Re: [PATCH char-misc 1/1] Drivers: hv: vmbus: Implement Direct Mode for stimer0
Date: Sat, 4 Nov 2017 00:01:30 +0800 [thread overview]
Message-ID: <201711032301.kGU7MOUE%fengguang.wu@intel.com> (raw)
In-Reply-To: <20171031221849.12117-1-mikelley@exchange.microsoft.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Hi Michael,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on char-misc/master]
url: https://github.com/0day-ci/linux/commits/mikelley-exchange-microsoft-com/Drivers-hv-vmbus-Implement-Direct-Mode-for-stimer0/20171103-214519
config: x86_64-rhel (attached as .config)
compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901
reproduce:
# save the attached .config to linux build tree
make ARCH=x86_64
All errors (new ones prefixed by >>):
>> ERROR: "hv_deallocate_stimer0_irq" [drivers/hv/hv_vmbus.ko] undefined!
>> ERROR: "hv_allocate_stimer0_irq" [drivers/hv/hv_vmbus.ko] undefined!
>> ERROR: "hv_ack_stimer0_interrupt" [drivers/hv/hv_vmbus.ko] undefined!
---
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: 40097 bytes --]
next prev parent reply other threads:[~2017-11-03 16:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 22:18 mikelley
2017-11-01 12:00 ` Vitaly Kuznetsov
2017-11-01 13:41 ` Vitaly Kuznetsov
2017-11-30 18:08 ` Michael Kelley (EOSG)
2017-11-01 14:51 ` Thomas Gleixner
2017-11-01 16:19 ` Thomas Gleixner
2017-11-01 16:21 ` Michael Kelley (EOSG)
2017-11-30 18:08 ` Michael Kelley (EOSG)
2017-11-03 16:01 ` kbuild test robot [this message]
2017-11-03 22:55 ` kbuild test robot
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=201711032301.kGU7MOUE%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=apw@canonical.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=kbuild-all@01.org \
--cc=kys@microsoft.com \
--cc=leann.ogasawara@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.cerri@canonical.com \
--cc=mikelley@exchange.microsoft.com \
--cc=mikelley@microsoft.com \
--cc=olaf@aepfle.de \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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
all inboxes | Powered by JetHome®