From: kernel test robot <lkp@intel.com>
To: Xianwei Zhao via B4 Relay
<devnull+xianwei.zhao.amlogic.com@kernel.org>,
Sunny Luo <sunny.luo@amlogic.com>,
Mark Brown <broonie@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, linux-amlogic@lists.infradead.org,
linux-spi@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Xianwei Zhao <xianwei.zhao@amlogic.com>
Subject: Re: [PATCH 2/3] spi: Add Amlogic SPISG driver
Date: Thu, 5 Jun 2025 16:41:06 +0800 [thread overview]
Message-ID: <202506051609.8GLrHoaR-lkp@intel.com> (raw)
In-Reply-To: <20250604-spisg-v1-2-5893dbe9d953@amlogic.com>
Hi Xianwei,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 57cf46cd1fe351846e1b065ca9546eef66675ecd]
url: https://github.com/intel-lab-lkp/linux/commits/Xianwei-Zhao-via-B4-Relay/dt-bindings-spi-Add-binding-document-of-Amlogic-SPISG-controller/20250604-154302
base: 57cf46cd1fe351846e1b065ca9546eef66675ecd
patch link: https://lore.kernel.org/r/20250604-spisg-v1-2-5893dbe9d953%40amlogic.com
patch subject: [PATCH 2/3] spi: Add Amlogic SPISG driver
config: microblaze-randconfig-r123-20250605 (https://download.01.org/0day-ci/archive/20250605/202506051609.8GLrHoaR-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 14.3.0
reproduce: (https://download.01.org/0day-ci/archive/20250605/202506051609.8GLrHoaR-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/202506051609.8GLrHoaR-lkp@intel.com/
sparse warnings: (new ones prefixed by >>)
>> drivers/spi/spi-amlogic-spisg.c:929:24: sparse: sparse: symbol 'amlogic_spisg_driver' was not declared. Should it be static?
vim +/amlogic_spisg_driver +929 drivers/spi/spi-amlogic-spisg.c
928
> 929 struct platform_driver amlogic_spisg_driver = {
930 .probe = aml_spicc_probe,
931 .remove = aml_spicc_remove,
932 .shutdown = aml_spicc_shutdown,
933 .driver = {
934 .name = "amlogic-spisg",
935 .of_match_table = of_match_ptr(amlogic_spisg_of_match),
936 .pm = &amlogic_spicc_pm_ops,
937 },
938 };
939
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
_______________________________________________
linux-amlogic mailing list
linux-amlogic@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-amlogic
next prev parent reply other threads:[~2025-06-05 8:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-04 7:40 [PATCH 0/3] support for amlogic the new SPI IP Xianwei Zhao via B4 Relay
2025-06-04 7:40 ` [PATCH 1/3] dt-bindings: spi: Add binding document of Amlogic SPISG controller Xianwei Zhao via B4 Relay
2025-06-04 7:40 ` [PATCH 2/3] spi: Add Amlogic SPISG driver Xianwei Zhao via B4 Relay
2025-06-05 8:41 ` kernel test robot [this message]
2025-06-10 16:48 ` neil.armstrong
2025-06-12 9:53 ` Xianwei Zhao
2025-06-04 7:40 ` [PATCH 3/3] MAINTAINERS: Add an entry for Amlogic spi driver Xianwei Zhao via B4 Relay
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=202506051609.8GLrHoaR-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=devnull+xianwei.zhao.amlogic.com@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=robh@kernel.org \
--cc=sunny.luo@amlogic.com \
--cc=xianwei.zhao@amlogic.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