From: kernel test robot <lkp@intel.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [axboe-block:rw_iter 133/133] drivers/fsi/fsi-scom.c:517:11: error: initialization from incompatible pointer type
Date: Sun, 7 Apr 2024 08:42:31 +0800 [thread overview]
Message-ID: <202404070837.DdPET6fd-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux-block.git rw_iter
head: 1a95bcd36c1c2fd1c92f33b5ea95c2e0a5667100
commit: 1a95bcd36c1c2fd1c92f33b5ea95c2e0a5667100 [133/133] REMOVE ->read() and ->write()
config: x86_64-randconfig-005-20240407 (https://download.01.org/0day-ci/archive/20240407/202404070837.DdPET6fd-lkp@intel.com/config)
compiler: gcc-7 (Ubuntu 7.5.0-6ubuntu2) 7.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240407/202404070837.DdPET6fd-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202404070837.DdPET6fd-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/fsi/fsi-scom.c:517:3: error: 'const struct file_operations' has no member named 'read'
.read = scom_read,
^~~~
drivers/fsi/fsi-scom.c:517:11: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
.read = scom_read,
^~~~~~~~~
drivers/fsi/fsi-scom.c:517:11: note: (near initialization for 'scom_fops')
>> drivers/fsi/fsi-scom.c:517:11: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
drivers/fsi/fsi-scom.c:517:11: note: (near initialization for 'scom_fops.compat_ioctl')
drivers/fsi/fsi-scom.c:518:3: error: 'const struct file_operations' has no member named 'write'
.write = scom_write,
^~~~~
drivers/fsi/fsi-scom.c:518:12: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
.write = scom_write,
^~~~~~~~~~
drivers/fsi/fsi-scom.c:518:12: note: (near initialization for 'scom_fops')
drivers/fsi/fsi-scom.c:518:12: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
drivers/fsi/fsi-scom.c:518:12: note: (near initialization for 'scom_fops.fsync')
cc1: some warnings being treated as errors
--
drivers/iio/imu/adis16400.c:237:3: error: 'const struct file_operations' has no member named 'read'
.read = adis16400_show_serial_number,
^~~~
drivers/iio/imu/adis16400.c:237:10: error: positional initialization of field in 'struct' declared with 'designated_init' attribute [-Werror=designated-init]
.read = adis16400_show_serial_number,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/iio/imu/adis16400.c:237:10: note: (near initialization for 'adis16400_serial_number_fops')
>> drivers/iio/imu/adis16400.c:237:10: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
drivers/iio/imu/adis16400.c:237:10: note: (near initialization for 'adis16400_serial_number_fops.fallocate')
cc1: some warnings being treated as errors
vim +517 drivers/fsi/fsi-scom.c
d8f4587655f968 Benjamin Herrenschmidt 2018-06-20 512
680ca6dcf5c222 Christopher Bostic 2017-06-06 513 static const struct file_operations scom_fops = {
680ca6dcf5c222 Christopher Bostic 2017-06-06 514 .owner = THIS_MODULE,
d8f4587655f968 Benjamin Herrenschmidt 2018-06-20 515 .open = scom_open,
680ca6dcf5c222 Christopher Bostic 2017-06-06 516 .llseek = scom_llseek,
680ca6dcf5c222 Christopher Bostic 2017-06-06 @517 .read = scom_read,
680ca6dcf5c222 Christopher Bostic 2017-06-06 518 .write = scom_write,
6b293258cded9c Benjamin Herrenschmidt 2018-06-12 519 .unlocked_ioctl = scom_ioctl,
680ca6dcf5c222 Christopher Bostic 2017-06-06 520 };
680ca6dcf5c222 Christopher Bostic 2017-06-06 521
:::::: The code at line 517 was first introduced by commit
:::::: 680ca6dcf5c222765cb2fb22959c5282865b6655 drivers/fsi: Add SCOM FSI client device driver
:::::: TO: Christopher Bostic <cbostic@linux.vnet.ibm.com>
:::::: CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-04-07 0:42 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=202404070837.DdPET6fd-lkp@intel.com \
--to=lkp@intel.com \
--cc=axboe@kernel.dk \
--cc=oe-kbuild-all@lists.linux.dev \
/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.