From: kbuild test robot <lkp@intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: kbuild-all@01.org, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>, Lv Zheng <lv.zheng@intel.com>,
linux-acpi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
devel@acpica.org, "Moore, Robert" <robert.moore@intel.com>
Subject: Re: [PATCH v2] acpi: configfs: Unload SSDT on configfs entry removal
Date: Sat, 3 Jun 2017 00:19:06 +0800 [thread overview]
Message-ID: <201706030041.zEMlyEDv%fengguang.wu@intel.com> (raw)
In-Reply-To: <3e2e6c99-a833-5c98-a5d0-ae5eddfbefe5@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
Hi Jan,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.12-rc3 next-20170602]
[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/Jan-Kiszka/acpi-configfs-Unload-SSDT-on-configfs-entry-removal/20170602-165617
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-allmodconfig (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=i386
All errors (new ones prefixed by >>):
>> ERROR: "acpi_tb_unload_table" [drivers/acpi/acpi_configfs.ko] undefined!
>> ERROR: "acpi_tb_install_and_load_table" [drivers/acpi/acpi_configfs.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: 60138 bytes --]
prev parent reply other threads:[~2017-06-02 16:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-02 7:06 Jan Kiszka
2017-06-02 16:19 ` kbuild test robot [this message]
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=201706030041.zEMlyEDv%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=devel@acpica.org \
--cc=jan.kiszka@siemens.com \
--cc=kbuild-all@01.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lv.zheng@intel.com \
--cc=rjw@rjwysocki.net \
--cc=robert.moore@intel.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®