From: kernel test robot <lkp@intel.com>
To: "Derek J. Clark" <derekjohn.clark@gmail.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>,
"Derek J . Clark" <derekjohn.clark@gmail.com>,
platform-driver-x86@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/4] platform/x86: (ayn-ec) Add PWM Fan HWMON Interface
Date: Sat, 26 Jul 2025 18:57:32 +0800 [thread overview]
Message-ID: <202507261841.lk1Z3fqj-lkp@intel.com> (raw)
In-Reply-To: <20250725004533.63537-1-derekjohn.clark@gmail.com>
Hi Derek,
kernel test robot noticed the following build warnings:
[auto build test WARNING on groeck-staging/hwmon-next]
[also build test WARNING on linus/master v6.16-rc7 next-20250725]
[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/Derek-J-Clark/platform-x86-ayn-ec-Add-Temperature-Sensors/20250725-084850
base: https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link: https://lore.kernel.org/r/20250725004533.63537-1-derekjohn.clark%40gmail.com
patch subject: [PATCH 1/4] platform/x86: (ayn-ec) Add PWM Fan HWMON Interface
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20250726/202507261841.lk1Z3fqj-lkp@intel.com/config)
compiler: clang version 20.1.8 (https://github.com/llvm/llvm-project 87f0227cb60147a26a1eeb4fb06e3b505e9c7261)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250726/202507261841.lk1Z3fqj-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/202507261841.lk1Z3fqj-lkp@intel.com/
All warnings (new ones prefixed by >>):
drivers/platform/x86/ayn-ec.c:526:6: warning: unused variable 'ret' [-Wunused-variable]
526 | int ret;
| ^~~
>> drivers/platform/x86/ayn-ec.c:557:35: warning: unused variable 'ayn_dmi_table' [-Wunused-const-variable]
557 | static const struct dmi_system_id ayn_dmi_table[] = {
| ^~~~~~~~~~~~~
2 warnings generated.
vim +/ayn_dmi_table +557 drivers/platform/x86/ayn-ec.c
521
522 static int ayn_ec_probe(struct platform_device *pdev)
523 {
524 struct device *dev = &pdev->dev;
525 struct device *hwdev;
> 526 int ret;
527
528 hwdev = devm_hwmon_device_register_with_info(dev, "aynec", NULL,
529 &ayn_ec_chip_info,
530 ayn_sensors_groups);
531 return PTR_ERR_OR_ZERO(hwdev);
532 }
533
534 static struct platform_driver ayn_ec_driver = {
535 .driver = {
536 .name = "ayn-ec",
537 },
538 .probe = ayn_ec_probe,
539 };
540
541 static struct platform_device *ayn_ec_device;
542
543 static int __init ayn_ec_init(void)
544 {
545 ayn_ec_device = platform_create_bundle(&ayn_ec_driver, ayn_ec_probe,
546 NULL, 0, NULL, 0);
547
548 return PTR_ERR_OR_ZERO(ayn_ec_device);
549 }
550
551 static void __exit ayn_ec_exit(void)
552 {
553 platform_device_unregister(ayn_ec_device);
554 platform_driver_unregister(&ayn_ec_driver);
555 }
556
> 557 static const struct dmi_system_id ayn_dmi_table[] = {
558 {
559 .matches = {
560 DMI_EXACT_MATCH(DMI_BOARD_VENDOR, "ayn"),
561 DMI_EXACT_MATCH(DMI_BOARD_NAME, "Loki Max"),
562 },
563 .driver_data = (void *)ayn_loki_max,
564 },
565 {
566 .matches = {
567 DMI_EXACT_MATCH(DMI_BOARD_VENDOR, "ayn"),
568 DMI_EXACT_MATCH(DMI_BOARD_NAME, "Loki MiniPro"),
569 },
570 .driver_data = (void *)ayn_loki_minipro,
571 },
572 {
573 .matches = {
574 DMI_EXACT_MATCH(DMI_BOARD_VENDOR, "ayn"),
575 DMI_EXACT_MATCH(DMI_BOARD_NAME, "Loki Zero"),
576 },
577 .driver_data = (void *)ayn_loki_zero,
578 },
579 {
580 .matches = {
581 DMI_EXACT_MATCH(DMI_BOARD_VENDOR, "Tectoy"),
582 DMI_EXACT_MATCH(DMI_BOARD_NAME, "Zeenix Lite"),
583 },
584 .driver_data = (void *)tactoy_zeenix_lite,
585 },
586 {},
587 };
588
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2025-07-26 10:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-25 0:45 Derek J. Clark
2025-07-25 0:45 ` [PATCH 2/4] platform/x86: (ayn-ec) Add Temperature Sensors Derek J. Clark
2025-07-25 15:29 ` ALOK TIWARI
2025-07-26 15:50 ` David Box
2025-07-26 17:52 ` Derek John Clark
2025-07-25 0:45 ` [PATCH 3/4] platform/x86: (ayn-ec) Add RGB Interface Derek J. Clark
2025-07-25 0:45 ` [PATCH 4/4] platform/x86: (ayn-ec) Add Ayn EC Platform Documentation Derek J. Clark
2025-07-25 15:08 ` [PATCH 1/4] platform/x86: (ayn-ec) Add PWM Fan HWMON Interface ALOK TIWARI
2025-07-26 2:48 ` Derek J. Clark
2025-07-26 10:57 ` kernel test robot [this message]
2025-07-26 11:43 ` kernel test robot
2025-07-26 12:06 ` kernel test robot
2025-07-26 13:20 ` kernel test robot
2025-07-26 15:34 ` kernel test robot
2025-07-26 15:47 ` David Box
2025-07-26 17:51 ` Derek John Clark
2025-07-26 17:21 ` kernel test robot
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=202507261841.lk1Z3fqj-lkp@intel.com \
--to=lkp@intel.com \
--cc=derekjohn.clark@gmail.com \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=platform-driver-x86@vger.kernel.org \
/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®