From: kernel test robot <rong.a.chen@intel.com>
To: Jarkko Nikula <jarkko.nikula@linux.intel.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
"Felipe Balbi (Intel)" <balbi@kernel.org>,
Raymond Tan <raymond.tan@intel.com>
Subject: [linux-next:master 6016/13550] drivers/counter/intel-qep.c:11:1: iwyu: warning: superfluous #include <linux/bitops.h>
Date: Mon, 28 Jun 2021 09:58:32 +0800 [thread overview]
Message-ID: <20210628015832.GI237458@shao2-debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 2267 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 8702f95941c215501826ea8743a8b64b83479209
commit: b711f687a1c1c14c2da589e84e4f61b975196951 [6016/13550] counter: Add support for Intel Quadrature Encoder Peripheral
config: x86_64-randconfig-b001-20210628 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project 59558129276098d62046c8cda92240d292cbfb1c)
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
# apt-get install iwyu # include-what-you-use
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=b711f687a1c1c14c2da589e84e4f61b975196951
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout b711f687a1c1c14c2da589e84e4f61b975196951
# save the attached .config to linux build tree
mkdir build_dir
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross C=1 CHECK=iwyu O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/counter/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
iwyu warnings: (new ones prefixed by >>)
>> drivers/counter/intel-qep.c:11:1: iwyu: warning: superfluous #include <linux/bitops.h>
vim +11 drivers/counter/intel-qep.c
b711f687a1c1c1 Jarkko Nikula 2021-06-02 @11 #include <linux/bitops.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 12 #include <linux/counter.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 13 #include <linux/kernel.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 14 #include <linux/module.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 15 #include <linux/mutex.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 16 #include <linux/pci.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 17 #include <linux/pm_runtime.h>
b711f687a1c1c1 Jarkko Nikula 2021-06-02 18
---
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: 43918 bytes --]
[-- Attachment #3: Type: text/plain, Size: 149 bytes --]
_______________________________________________
kbuild mailing list -- kbuild@lists.01.org
To unsubscribe send an email to kbuild-leave@lists.01.org
reply other threads:[~2021-06-28 1:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20210628015832.GI237458@shao2-debian \
--to=rong.a.chen@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=balbi@kernel.org \
--cc=jarkko.nikula@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=raymond.tan@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