From: kbuild test robot <lkp@intel.com>
To: yankejian <yankejian@huawei.com>
Cc: kbuild-all@01.org, rjw@rjwysocki.net, lenb@kernel.org,
davem@davemloft.net, liguozhu@huawei.com,
yisen.zhuang@huawei.com, huangdaode@hisilicon.com,
lipeng321@huawei.com, yankejian@huawei.com,
linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH] ACPI: Add phylib support code for mdio
Date: Thu, 3 Dec 2015 12:45:29 +0800 [thread overview]
Message-ID: <201512031249.B2uXALRv%fengguang.wu@intel.com> (raw)
In-Reply-To: <1449107683-69717-1-git-send-email-yankejian@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Hi yankejian,
[auto build test ERROR on pm/linux-next]
[also build test ERROR on v4.4-rc3 next-20151202]
url: https://github.com/0day-ci/linux/commits/yankejian/ACPI-Add-phylib-support-code-for-mdio/20151203-115039
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: i386-randconfig-s1-201548 (attached as .config)
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
All errors (new ones prefixed by >>):
>> make[3]: *** No rule to make target 'drivers/acpi/mcfg.o', needed by 'drivers/acpi/built-in.o'.
make[3]: Target '__build' not remade because of errors.
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/octet-stream, Size: 23950 bytes --]
next prev parent reply other threads:[~2015-12-03 4:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 1:54 yankejian
2015-12-03 4:45 ` kbuild test robot [this message]
2015-12-03 4:55 ` kbuild test robot
2015-12-03 10:47 ` Graeme Gregory
2015-12-08 19:55 ` Al Stone
2015-12-09 10:31 ` Yankejian (Hackim Yim)
2015-12-10 1:27 ` Yankejian (Hackim Yim)
2016-01-12 12:12 ` Yankejian (Hackim Yim)
2016-01-12 12:39 ` Graeme Gregory
2016-01-13 3:03 ` Yankejian (Hackim Yim)
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=201512031249.B2uXALRv%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=huangdaode@hisilicon.com \
--cc=kbuild-all@01.org \
--cc=lenb@kernel.org \
--cc=liguozhu@huawei.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=rjw@rjwysocki.net \
--cc=yankejian@huawei.com \
--cc=yisen.zhuang@huawei.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®