From: kernel test robot <lkp@intel.com>
To: "Damien Riégel" <damien.riegel@silabs.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev
Subject: Re: [RFC 3/6] greybus: cpc: add SPI driver
Date: Sun, 6 Jul 2025 09:10:50 +0800 [thread overview]
Message-ID: <202507060806.1rBpnamP-lkp@intel.com> (raw)
In-Reply-To: <20250705004036.3828-4-damien.riegel@silabs.com>
Hi Damien,
[This is a private test report for your RFC patch.]
kernel test robot noticed the following build warnings:
[auto build test WARNING on staging/staging-testing]
[also build test WARNING on staging/staging-next staging/staging-linus linus/master v6.16-rc4 next-20250704]
[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/Damien-Ri-gel/greybus-move-host-controller-drivers-comment-in-Makefile/20250705-090138
base: staging/staging-testing
patch link: https://lore.kernel.org/r/20250705004036.3828-4-damien.riegel%40silabs.com
patch subject: [RFC 3/6] greybus: cpc: add SPI driver
config: hexagon-allyesconfig (https://download.01.org/0day-ci/archive/20250706/202507060806.1rBpnamP-lkp@intel.com/config)
compiler: clang version 21.0.0git (https://github.com/llvm/llvm-project 61529d9e36fa86782a2458e6bdeedf7f376ef4b5)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250706/202507060806.1rBpnamP-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/202507060806.1rBpnamP-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/greybus/cpc/spi.c:566:35: warning: unused variable 'cpc_spi_ids' [-Wunused-const-variable]
566 | static const struct spi_device_id cpc_spi_ids[] = {
| ^~~~~~~~~~~
1 warning generated.
vim +/cpc_spi_ids +566 drivers/greybus/cpc/spi.c
565
> 566 static const struct spi_device_id cpc_spi_ids[] = {
567 { .name = "cpc-spi" },
568 {},
569 };
570 MODULE_DEVICE_TABLE(spi, cpc_spi_ids);
571
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-06 1:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-05 0:40 [RFC 0/6] Introducing CPC support in Greybus Damien Riégel
2025-07-05 0:40 ` [RFC 1/6] greybus: move host controller drivers comment in Makefile Damien Riégel
2025-07-16 13:20 ` Greg Kroah-Hartman
2025-07-05 0:40 ` [RFC 2/6] greybus: cpc: add core logic Damien Riégel
2025-07-05 23:35 ` kernel test robot
2025-07-16 13:21 ` Greg Kroah-Hartman
2025-07-05 0:40 ` [RFC 3/6] greybus: cpc: add SPI driver Damien Riégel
2025-07-06 1:10 ` kernel test robot [this message]
2025-07-05 0:40 ` [RFC 4/6] greybus: add API for async unidirectional transfer Damien Riégel
2025-07-16 13:21 ` Greg Kroah-Hartman
2025-07-05 0:40 ` [RFC 5/6] greybus: match device with bundle ID Damien Riégel
2025-07-16 13:19 ` Greg Kroah-Hartman
2025-07-05 0:40 ` [RFC 6/6] greybus: add class driver for Silabs Bluetooth Damien Riégel
2025-07-06 0:39 ` kernel test robot
2025-07-16 13:23 ` Greg Kroah-Hartman
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=202507060806.1rBpnamP-lkp@intel.com \
--to=lkp@intel.com \
--cc=damien.riegel@silabs.com \
--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 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.