From: kernel test robot <lkp@intel.com>
To: Haixu Cui <quic_haixcui@quicinc.com>,
andriy.shevchenko@intel.com, harald.mommer@oss.qualcomm.com,
quic_msavaliy@quicinc.com, broonie@kernel.org,
virtio-dev@lists.linux.dev, viresh.kumar@linaro.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
hdanton@sina.com, qiang4.zhang@linux.intel.com,
alex.bennee@linaro.org
Cc: oe-kbuild-all@lists.linux.dev, quic_ztu@quicinc.com
Subject: Re: [PATCH v4 3/3] SPI: Add virtio SPI driver
Date: Thu, 21 Aug 2025 10:22:13 +0800 [thread overview]
Message-ID: <202508211051.cuOjaH00-lkp@intel.com> (raw)
In-Reply-To: <20250820084944.84505-4-quic_haixcui@quicinc.com>
Hi Haixu,
kernel test robot noticed the following build warnings:
[auto build test WARNING on broonie-spi/for-next]
[also build test WARNING on linus/master v6.17-rc2 next-20250820]
[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#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Haixu-Cui/virtio-Add-ID-for-virtio-SPI/20250820-165441
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
patch link: https://lore.kernel.org/r/20250820084944.84505-4-quic_haixcui%40quicinc.com
patch subject: [PATCH v4 3/3] SPI: Add virtio SPI driver
config: loongarch-allyesconfig (https://download.01.org/0day-ci/archive/20250821/202508211051.cuOjaH00-lkp@intel.com/config)
compiler: clang version 22.0.0git (https://github.com/llvm/llvm-project 93d24b6b7b148c47a2fa228a4ef31524fa1d9f3f)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250821/202508211051.cuOjaH00-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/202508211051.cuOjaH00-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/spi/spi-virtio.c:373:45: warning: cast from 'void (*)(struct virtio_device *)' to 'void (*)(void *)' converts to incompatible function type [-Wcast-function-type-strict]
373 | err = devm_add_action_or_reset(&vdev->dev, (void (*)(void *))virtio_spi_del_vq, vdev);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
include/linux/device/devres.h:166:34: note: expanded from macro 'devm_add_action_or_reset'
166 | __devm_add_action_or_reset(dev, action, data, #action)
| ^~~~~~
1 warning generated.
vim +373 drivers/spi/spi-virtio.c
333
334 static int virtio_spi_probe(struct virtio_device *vdev)
335 {
336 struct virtio_spi_priv *priv;
337 struct spi_controller *ctrl;
338 int err;
339 u32 bus_num;
340
341 ctrl = devm_spi_alloc_host(&vdev->dev, sizeof(*priv));
342 if (!ctrl)
343 return -ENOMEM;
344
345 priv = spi_controller_get_devdata(ctrl);
346 priv->vdev = vdev;
347 vdev->priv = priv;
348
349 device_set_node(&ctrl->dev, dev_fwnode(&vdev->dev));
350
351 /* Setup ACPI node for controlled devices which will be probed through ACPI. */
352 ACPI_COMPANION_SET(&vdev->dev, ACPI_COMPANION(vdev->dev.parent));
353
354 dev_set_drvdata(&vdev->dev, ctrl);
355
356 err = device_property_read_u32(&vdev->dev, "spi,bus-num", &bus_num);
357 if (!err && bus_num <= S16_MAX)
358 ctrl->bus_num = bus_num;
359 else
360 ctrl->bus_num = -1;
361
362 virtio_spi_read_config(vdev);
363
364 ctrl->transfer_one = virtio_spi_transfer_one;
365
366 err = virtio_spi_find_vqs(priv);
367 if (err) {
368 dev_err_probe(&vdev->dev, err, "Cannot setup virtqueues\n");
369 return err;
370 }
371
372 /* Register cleanup for virtqueues using devm */
> 373 err = devm_add_action_or_reset(&vdev->dev, (void (*)(void *))virtio_spi_del_vq, vdev);
374 if (err) {
375 dev_err_probe(&vdev->dev, err, "Cannot register virtqueue cleanup\n");
376 return err;
377 }
378
379 /* Use devm version to register controller */
380 err = devm_spi_register_controller(&vdev->dev, ctrl);
381 if (err) {
382 dev_err_probe(&vdev->dev, err, "Cannot register controller\n");
383 return err;
384 }
385
386 return 0;
387 }
388
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-08-21 2:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 8:49 [PATCH v4 0/3] Virtio SPI Linux driver Haixu Cui
2025-08-20 8:49 ` [PATCH v4 1/3] virtio: Add ID for virtio SPI Haixu Cui
2025-08-20 8:49 ` [PATCH v4 2/3] virtio-spi: Add virtio-spi.h Haixu Cui
2025-08-21 8:42 ` Michael S. Tsirkin
2025-08-25 9:12 ` Haixu Cui
2025-08-28 10:19 ` Michael S. Tsirkin
2025-08-21 8:45 ` Michael S. Tsirkin
2025-08-25 9:19 ` Haixu Cui
2025-08-28 10:34 ` Michael S. Tsirkin
2025-09-03 6:55 ` Haixu Cui
2025-09-03 7:00 ` Haixu Cui
[not found] ` <aKXaI0SAAMaHMZM9@smile.fi.intel.com>
2025-08-25 8:35 ` Haixu Cui
2025-08-20 8:49 ` [PATCH v4 3/3] SPI: Add virtio SPI driver Haixu Cui
2025-08-21 2:22 ` kernel test robot [this message]
[not found] ` <aKXePVShWzXGi8yP@smile.fi.intel.com>
2025-08-25 9:01 ` Haixu Cui
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=202508211051.cuOjaH00-lkp@intel.com \
--to=lkp@intel.com \
--cc=alex.bennee@linaro.org \
--cc=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--cc=harald.mommer@oss.qualcomm.com \
--cc=hdanton@sina.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=qiang4.zhang@linux.intel.com \
--cc=quic_haixcui@quicinc.com \
--cc=quic_msavaliy@quicinc.com \
--cc=quic_ztu@quicinc.com \
--cc=viresh.kumar@linaro.org \
--cc=virtio-dev@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