From: kernel test robot <lkp@intel.com>
To: Rosen Penev <rosenp@gmail.com>, linux-spi@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] spi: rb4xx: add COMPILE_TEST support
Date: Wed, 27 Aug 2025 04:35:27 +0800 [thread overview]
Message-ID: <202508270444.t2WdWo8x-lkp@intel.com> (raw)
In-Reply-To: <20250821033534.638157-1-rosenp@gmail.com>
Hi Rosen,
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-rc3 next-20250826]
[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/Rosen-Penev/spi-rb4xx-add-COMPILE_TEST-support/20250821-113701
base: https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
patch link: https://lore.kernel.org/r/20250821033534.638157-1-rosenp%40gmail.com
patch subject: [PATCH] spi: rb4xx: add COMPILE_TEST support
config: m68k-randconfig-r073-20250827 (https://download.01.org/0day-ci/archive/20250827/202508270444.t2WdWo8x-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250827/202508270444.t2WdWo8x-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/202508270444.t2WdWo8x-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/spi/spi-rb4xx.c:200:34: warning: 'rb4xx_spi_dt_match' defined but not used [-Wunused-const-variable=]
200 | static const struct of_device_id rb4xx_spi_dt_match[] = {
| ^~~~~~~~~~~~~~~~~~
vim +/rb4xx_spi_dt_match +200 drivers/spi/spi-rb4xx.c
05aec357871f89 Bert Vermeulen 2015-04-15 199
9a436c62fbb4c5 Christopher Hill 2020-05-21 @200 static const struct of_device_id rb4xx_spi_dt_match[] = {
9a436c62fbb4c5 Christopher Hill 2020-05-21 201 { .compatible = "mikrotik,rb4xx-spi" },
9a436c62fbb4c5 Christopher Hill 2020-05-21 202 { },
9a436c62fbb4c5 Christopher Hill 2020-05-21 203 };
9a436c62fbb4c5 Christopher Hill 2020-05-21 204 MODULE_DEVICE_TABLE(of, rb4xx_spi_dt_match);
9a436c62fbb4c5 Christopher Hill 2020-05-21 205
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-26 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-21 3:35 Rosen Penev
2025-08-26 20:35 ` kernel test robot [this message]
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=202508270444.t2WdWo8x-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rosenp@gmail.com \
/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
all inboxes | Powered by JetHome®