From: kernel test robot <lkp@intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
devel@driverdev.osuosl.org
Subject: [driver-core:const_driver 16/23] drivers/cdx/cdx.c:648:12: error: incompatible function pointer types initializing 'int (*)(struct device *, const struct device_driver *)' with an expression of type 'int (struct device *, struct device_driver *)'
Date: Mon, 17 Jun 2024 07:42:45 +0800 [thread overview]
Message-ID: <202406170739.qxdbTrrC-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git const_driver
head: 59a02fe9d47c712050ae1895d753dd46ce97f357
commit: 271b7e9b52810c0931a92496d9de0e3e07be51e0 [16/23] driver core: have match() callback in struct bus_type take a const *
config: arm64-randconfig-004-20240617 (https://download.01.org/0day-ci/archive/20240617/202406170739.qxdbTrrC-lkp@intel.com/config)
compiler: clang version 15.0.7 (https://github.com/llvm/llvm-project 8dfdcc7b7bf66834a761bd8de445840ef68e4d1a)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240617/202406170739.qxdbTrrC-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/202406170739.qxdbTrrC-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/cdx/cdx.c:648:12: error: incompatible function pointer types initializing 'int (*)(struct device *, const struct device_driver *)' with an expression of type 'int (struct device *, struct device_driver *)' [-Werror,-Wincompatible-function-pointer-types]
.match = cdx_bus_match,
^~~~~~~~~~~~~
1 error generated.
vim +648 drivers/cdx/cdx.c
2959ab247061e6 Nipun Gupta 2023-03-13 645
2959ab247061e6 Nipun Gupta 2023-03-13 646 struct bus_type cdx_bus_type = {
2959ab247061e6 Nipun Gupta 2023-03-13 647 .name = "cdx",
2959ab247061e6 Nipun Gupta 2023-03-13 @648 .match = cdx_bus_match,
2959ab247061e6 Nipun Gupta 2023-03-13 649 .probe = cdx_probe,
2959ab247061e6 Nipun Gupta 2023-03-13 650 .remove = cdx_remove,
2959ab247061e6 Nipun Gupta 2023-03-13 651 .shutdown = cdx_shutdown,
2959ab247061e6 Nipun Gupta 2023-03-13 652 .dma_configure = cdx_dma_configure,
b8c5ff76059ded Nipun Gupta 2023-06-05 653 .dma_cleanup = cdx_dma_cleanup,
2959ab247061e6 Nipun Gupta 2023-03-13 654 .bus_groups = cdx_bus_groups,
48a6c7bced2a78 Nipun Gupta 2023-03-13 655 .dev_groups = cdx_dev_groups,
2959ab247061e6 Nipun Gupta 2023-03-13 656 };
2959ab247061e6 Nipun Gupta 2023-03-13 657 EXPORT_SYMBOL_GPL(cdx_bus_type);
2959ab247061e6 Nipun Gupta 2023-03-13 658
:::::: The code at line 648 was first introduced by commit
:::::: 2959ab247061e67485d83b6af8feb3761ec08cb9 cdx: add the cdx bus driver
:::::: TO: Nipun Gupta <nipun.gupta@amd.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-06-16 23:43 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=202406170739.qxdbTrrC-lkp@intel.com \
--to=lkp@intel.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=llvm@lists.linux.dev \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).