From: kernel test robot <lkp@intel.com>
To: "Frédéric Pierret (fepitre)" <frederic.pierret@qubes-os.org>,
sre@kernel.org, linux-pm@vger.kernel.org, davem@davemloft.net,
ast@kernel.org, axboe@kernel.dk, johannes.berg@intel.com,
mkubecek@suse.cz
Cc: kbuild-all@lists.01.org, clang-built-linux@googlegroups.com,
"Frédéric Pierret (fepitre)" <frederic.pierret@qubes-os.org>
Subject: Re: [PATCH 1/2] Create uapi power_supply from enums and power_supply_is_* funcs
Date: Mon, 17 Aug 2020 01:38:55 +0800 [thread overview]
Message-ID: <202008170115.3zzjdfyl%lkp@intel.com> (raw)
In-Reply-To: <20200815081616.4986-1-frederic.pierret@qubes-os.org>
[-- Attachment #1: Type: text/plain, Size: 1973 bytes --]
Hi "Frédéric,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on power-supply/for-next]
[also build test ERROR on linus/master next-20200814]
[cannot apply to v5.8]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Fr-d-ric-Pierret-fepitre/Create-uapi-power_supply-from-enums-and-power_supply_is_-funcs/20200816-120329
base: https://git.kernel.org/pub/scm/linux/kernel/git/sre/linux-power-supply.git for-next
config: x86_64-randconfig-a006-20200816 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project ab9fc8bae805c785066779e76e7846aabad5609e)
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 >>):
>> error: include/uapi/linux/power_supply.h: missing "WITH Linux-syscall-note" for SPDX-License-Identifier
make[2]: *** [scripts/Makefile.headersinst:63: usr/include/linux/power_supply.h] Error 1
make[2]: Target '__headers' not remade because of errors.
make[1]: *** [Makefile:1258: headers] Error 2
make[1]: Target 'headers_install' not remade because of errors.
make: *** [Makefile:185: __sub-make] Error 2
make: Target 'headers_install' not remade because of errors.
---
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: 36406 bytes --]
prev parent reply other threads:[~2020-08-16 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 8:16 [PATCH 1/2] Create uapi power_supply from enums and power_supply_is_* funcs Frédéric Pierret (fepitre)
2020-08-15 8:16 ` [PATCH 2/2] uapi/linux/power_supply.h: add power_supply_is_str_property func Frédéric Pierret (fepitre)
2020-08-16 8:54 ` [PATCH 1/2] Create uapi power_supply from enums and power_supply_is_* funcs kernel test robot
2020-08-16 17:38 ` kernel 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=202008170115.3zzjdfyl%lkp@intel.com \
--to=lkp@intel.com \
--cc=ast@kernel.org \
--cc=axboe@kernel.dk \
--cc=clang-built-linux@googlegroups.com \
--cc=davem@davemloft.net \
--cc=frederic.pierret@qubes-os.org \
--cc=johannes.berg@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-pm@vger.kernel.org \
--cc=mkubecek@suse.cz \
--cc=sre@kernel.org \
/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