From: kernel test robot <lkp@intel.com>
To: Akshu Agrawal <akshu.agrawal@amd.com>
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
akshu.agrawal@amd.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
"open list:ACPI" <linux-acpi@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] ACPI: APD: Change name from ST to FCH
Date: Tue, 7 Jul 2020 22:33:52 +0800 [thread overview]
Message-ID: <202007072220.Oo7A49vs%lkp@intel.com> (raw)
In-Reply-To: <20200707100320.24625-1-akshu.agrawal@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1856 bytes --]
Hi Akshu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on linus/master v5.8-rc4 next-20200707]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Akshu-Agrawal/ACPI-APD-Change-name-from-ST-to-FCH/20200707-180843
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-randconfig-a006-20200707 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 02946de3802d3bc65bc9f2eb9b8d4969b5a7add8)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/x86/clk-st.c:11:10: fatal error: 'linux/platform_data/clk-st.h' file not found
#include <linux/platform_data/clk-st.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +11 drivers/clk/x86/clk-st.c
421bf6a1f061a6 Akshu Agrawal 2018-05-09 @11 #include <linux/platform_data/clk-st.h>
421bf6a1f061a6 Akshu Agrawal 2018-05-09 12 #include <linux/platform_device.h>
421bf6a1f061a6 Akshu Agrawal 2018-05-09 13
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 34592 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [PATCH 1/2] ACPI: APD: Change name from ST to FCH
Date: Tue, 07 Jul 2020 22:33:52 +0800 [thread overview]
Message-ID: <202007072220.Oo7A49vs%lkp@intel.com> (raw)
In-Reply-To: <20200707100320.24625-1-akshu.agrawal@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
Hi Akshu,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on pm/linux-next]
[also build test ERROR on linus/master v5.8-rc4 next-20200707]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Akshu-Agrawal/ACPI-APD-Change-name-from-ST-to-FCH/20200707-180843
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
config: x86_64-randconfig-a006-20200707 (attached as .config)
compiler: clang version 11.0.0 (https://github.com/llvm/llvm-project 02946de3802d3bc65bc9f2eb9b8d4969b5a7add8)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# install x86_64 cross compiling tool for clang build
# apt-get install binutils-x86-64-linux-gnu
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> drivers/clk/x86/clk-st.c:11:10: fatal error: 'linux/platform_data/clk-st.h' file not found
#include <linux/platform_data/clk-st.h>
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
vim +11 drivers/clk/x86/clk-st.c
421bf6a1f061a6 Akshu Agrawal 2018-05-09 @11 #include <linux/platform_data/clk-st.h>
421bf6a1f061a6 Akshu Agrawal 2018-05-09 12 #include <linux/platform_device.h>
421bf6a1f061a6 Akshu Agrawal 2018-05-09 13
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
[-- Attachment #2: config.gz --]
[-- Type: application/gzip, Size: 34592 bytes --]
next prev parent reply other threads:[~2020-07-07 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 10:02 [PATCH 1/2] ACPI: APD: Change name from ST to FCH Akshu Agrawal
2020-07-07 10:03 ` [PATCH 2/2] ACPI: APD: Add a fmw property is_raven Akshu Agrawal
2020-07-07 14:33 ` kernel test robot [this message]
2020-07-07 14:33 ` [PATCH 1/2] ACPI: APD: Change name from ST to FCH kernel test robot
2020-07-07 17:29 ` kernel test robot
2020-07-07 17:29 ` kernel 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=202007072220.Oo7A49vs%lkp@intel.com \
--to=lkp@intel.com \
--cc=akshu.agrawal@amd.com \
--cc=clang-built-linux@googlegroups.com \
--cc=kbuild-all@lists.01.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.