From: Rong Chen <rong.a.chen@intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
kbuild test robot <lkp@intel.com>
Cc: "Rafael J . Wysocki" <rjw@rjwysocki.net>,
Ferry Toth <fntoth@gmail.com>,
linux-acpi@vger.kernel.org, kbuild-all@01.org,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Len Brown <lenb@kernel.org>
Subject: Re: [kbuild-all] [PATCH v1] ACPI / platform: Unregister stale platform devices
Date: Wed, 4 Sep 2019 16:46:46 +0800 [thread overview]
Message-ID: <b664df76-f9a8-6c18-aaf5-877d10b9e36b@intel.com> (raw)
In-Reply-To: <20190902095249.GU2680@smile.fi.intel.com>
On 9/2/19 5:52 PM, Andy Shevchenko wrote:
> On Mon, Sep 02, 2019 at 02:38:05PM +0800, kbuild test robot wrote:
>> Hi Andy,
>>
>> I love your patch! Yet something to improve:
>>
>> [auto build test ERROR on linus/master]
>> [cannot apply to v5.3-rc6 next-20190830]
>> [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/Andy-Shevchenko/ACPI-platform-Unregister-stale-platform-devices/20190902-001307
>> config: x86_64-lkp (attached as .config)
>> compiler: gcc-7 (Debian 7.4.0-11) 7.4.0
>> 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//acpi/acpi_platform.c: In function 'acpi_platform_device_find_by_adev':
>>>> drivers//acpi/acpi_platform.c:38:8: error: implicit declaration of function 'bus_find_device_by_acpi_dev'; did you mean 'bus_find_device_by_name'? [-Werror=implicit-function-declaration]
> False positive, it has Depends-on tag for the dependency which is not yet in
> upstream.
>
> Btw, have you noticed double slash in the paths in your scripts for LKP?
> (Look above)
Hi Andy,
Thanks for the new finding, The double slash not always appears .
I think the double slash is not from our scripts.
Best Regards,
Rong Chen
next prev parent reply other threads:[~2019-09-04 8:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-30 14:34 [PATCH v1] ACPI / platform: Unregister stale platform devices Andy Shevchenko
2019-09-02 6:38 ` kbuild test robot
2019-09-02 9:52 ` Andy Shevchenko
2019-09-04 8:46 ` Rong Chen [this message]
2019-09-02 7:19 ` kbuild test robot
2019-09-02 9:55 ` Andy Shevchenko
2019-10-17 11:38 ` Andy Shevchenko
2019-10-17 21:57 ` Rafael J. Wysocki
2019-10-18 8:35 ` Andy Shevchenko
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=b664df76-f9a8-6c18-aaf5-877d10b9e36b@intel.com \
--to=rong.a.chen@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=fntoth@gmail.com \
--cc=kbuild-all@01.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=rjw@rjwysocki.net \
/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).