Hi Malloy,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: a81d020c58c2c6a55ebaf15846470a9ecb69bd1a
commit: e8483fcd43fc1dbb8d21bb7eacce804cbab6a7c6 [1294/1294] spi: add phytium spi support
config: arm64-randconfig-002-20241114 (https://download.01.org/0day-ci/archive/20241114/202411140310.Hie7iwxT-lkp@…)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241114/202411140310.Hie7iwxT-lkp@…)
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(a)intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411140310.Hie7iwxT-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/spi/spi-phytium-plat.c:192:36: warning: 'phytium_spi_acpi_match' defined but not used [-Wunused-const-variable=]
192 | static const struct acpi_device_id phytium_spi_acpi_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for HARDLOCKUP_DETECTOR
Depends on [n]: DEBUG_KERNEL [=n] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=n] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=y])
Selected by [y]:
- SDEI_WATCHDOG [=y] && <choice> && ARM_SDE_INTERFACE [=y] && !HARDLOCKUP_CHECK_TIMESTAMP [=n]
vim +/phytium_spi_acpi_match +192 drivers/spi/spi-phytium-plat.c
191
> 192 static const struct acpi_device_id phytium_spi_acpi_match[] = {
193 {"PHYT000E", 0},
194 {}
195 };
196 MODULE_DEVICE_TABLE(acpi, phytium_spi_acpi_match);
197
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Hi liuyun,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git OLK-6.6
head: 19640fb08a2ccfb131121859517dfdbc6a04ccb6
commit: 47a0b6f372d7f05822d021f86b21a34fd2142225 [1466/1466] cpufreq: Add cpufreq driver for LoongArch
config: loongarch-randconfig-001-20241114 (https://download.01.org/0day-ci/archive/20241114/202411140232.Npxt3xRi-lkp@…)
compiler: loongarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241114/202411140232.Npxt3xRi-lkp@…)
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(a)intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411140232.Npxt3xRi-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/cpufreq/loongson3-acpi-cpufreq.c:645:5: warning: no previous prototype for 'loongson3_set_mode' [-Wmissing-prototypes]
645 | int loongson3_set_mode(int mode, int freq_level)
| ^~~~~~~~~~~~~~~~~~
drivers/cpufreq/loongson3-acpi-cpufreq.c:835:14: warning: no previous prototype for 'load_update' [-Wmissing-prototypes]
835 | unsigned int load_update(struct core_data *core)
| ^~~~~~~~~~~
drivers/cpufreq/loongson3-acpi-cpufreq.c:1520:36: warning: 'processor_device_ids' defined but not used [-Wunused-const-variable=]
1520 | static const struct acpi_device_id processor_device_ids[] = {
| ^~~~~~~~~~~~~~~~~~~~
>> drivers/cpufreq/loongson3-acpi-cpufreq.c:89:12: warning: 'lasx_count_threshold' defined but not used [-Wunused-variable]
89 | static int lasx_count_threshold = 200;
| ^~~~~~~~~~~~~~~~~~~~
vim +/lasx_count_threshold +89 drivers/cpufreq/loongson3-acpi-cpufreq.c
85
86 /* threshold of core's get into msa */
87 static int msa_count_threshold = 200;
88 /* threshold of core's get into lasx */
> 89 static int lasx_count_threshold = 200;
90 /* other cores' upper load threshold when 1 core get into boost mode and enable msa/lasx */
91 static int load_threshold = 60;
92
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
Hi Tian,
FYI, the error/warning still remains.
tree: https://gitee.com/openeuler/kernel.git openEuler-1.0-LTS
head: a81d020c58c2c6a55ebaf15846470a9ecb69bd1a
commit: 00711bad7e372a30c4975ba43811ffa666aff0e1 [1294/1294] gpio: add phytium gpio driver
config: arm64-randconfig-001-20241114 (https://download.01.org/0day-ci/archive/20241114/202411140242.XxdoeZ1Z-lkp@…)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241114/202411140242.XxdoeZ1Z-lkp@…)
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(a)intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202411140242.XxdoeZ1Z-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/gpio/gpio-phytium-platform.c:30:36: warning: 'phytium_gpio_acpi_match' defined but not used [-Wunused-const-variable=]
30 | static const struct acpi_device_id phytium_gpio_acpi_match[] = {
| ^~~~~~~~~~~~~~~~~~~~~~~
Kconfig warnings: (for reference only)
WARNING: unmet direct dependencies detected for HARDLOCKUP_DETECTOR
Depends on [n]: DEBUG_KERNEL [=n] && !S390 && (HAVE_HARDLOCKUP_DETECTOR_PERF [=n] || HAVE_HARDLOCKUP_DETECTOR_ARCH [=y])
Selected by [y]:
- SDEI_WATCHDOG [=y] && <choice> && ARM_SDE_INTERFACE [=y] && !HARDLOCKUP_CHECK_TIMESTAMP [=n]
vim +/phytium_gpio_acpi_match +30 drivers/gpio/gpio-phytium-platform.c
29
> 30 static const struct acpi_device_id phytium_gpio_acpi_match[] = {
31 { "PHYT0001", 0 },
32 { }
33 };
34 MODULE_DEVICE_TABLE(acpi, phytium_gpio_acpi_match);
35
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki