public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jic23-iio:iio-iwyu-cleanups 37/75] drivers/iio/buffer/industrialio-buffer-cb.c:5:10: fatal error: linux/bitopsh: No such file or directory
Date: Mon, 1 Nov 2021 03:54:52 +0800	[thread overview]
Message-ID: <202111010346.7AEzOaBu-lkp@intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1928 bytes --]

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git iio-iwyu-cleanups
head:   48e71ff9c7e9c4491d72c616dd1a6c4ea509eb21
commit: 8a65a4d21dbcf15666887f12f62d337ffa4d36db [37/75] iio: industrialio-buffer-cb: Bring includes up to date.
config: x86_64-buildonly-randconfig-r003-20211031 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
        # https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git/commit/?id=8a65a4d21dbcf15666887f12f62d337ffa4d36db
        git remote add jic23-iio https://git.kernel.org/pub/scm/linux/kernel/git/jic23/iio.git
        git fetch --no-tags jic23-iio iio-iwyu-cleanups
        git checkout 8a65a4d21dbcf15666887f12f62d337ffa4d36db
        # save the attached .config to linux build tree
        mkdir build_dir
        make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash drivers/iio/buffer/

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/iio/buffer/industrialio-buffer-cb.c:5:10: fatal error: linux/bitopsh: No such file or directory
       5 | #include <linux/bitopsh>
         |          ^~~~~~~~~~~~~~~
   compilation terminated.


vim +5 drivers/iio/buffer/industrialio-buffer-cb.c

   > 5	#include <linux/bitopsh>
     6	#include <linux/bitmap.h>
     7	#include <linux/container_of.h>
     8	#include <linux/device.h>
     9	#include <linux/err.h>
    10	#include <linux/errno.h>
    11	#include <linux/export.h>
    12	#include <linux/list.h>
    13	#include <linux/module.h>
    14	#include <linux/slab.h>
    15	#include <linux/stddef.h>
    16	#include <linux/types.h>
    17	#include <linux/iio/iio.h>
    18	#include <linux/iio/buffer_impl.h>
    19	#include <linux/iio/consumer.h>
    20	

---
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: 41354 bytes --]

                 reply	other threads:[~2021-10-31 19:55 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=202111010346.7AEzOaBu-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.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