linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: oe-kbuild-all@lists.linux.dev, Jean Delvare <jdelvare@suse.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Alok Tiwari <alok.a.tiwari@oracle.com>,
	David Box <david.e.box@linux.intel.com>,
	"Derek J . Clark" <derekjohn.clark@gmail.com>,
	platform-driver-x86@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-hwmon@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: Re: [PATCH v3 3/4] platform/x86: (ayn-ec) Add RGB Interface
Date: Tue, 29 Jul 2025 07:36:57 +0800	[thread overview]
Message-ID: <202507290730.7XZMyOM7-lkp@intel.com> (raw)
In-Reply-To: <20250726204041.516440-4-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 next-20250728]
[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-PWM-Fan-HWMON-Interface/20250727-044332
base:   https://git.kernel.org/pub/scm/linux/kernel/git/groeck/linux-staging.git hwmon-next
patch link:    https://lore.kernel.org/r/20250726204041.516440-4-derekjohn.clark%40gmail.com
patch subject: [PATCH v3 3/4] platform/x86: (ayn-ec) Add RGB Interface
config: i386-randconfig-061-20250728 (https://download.01.org/0day-ci/archive/20250729/202507290730.7XZMyOM7-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/20250729/202507290730.7XZMyOM7-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/202507290730.7XZMyOM7-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
   drivers/platform/x86/ayn-ec.c:87:5: sparse: sparse: symbol 'ayn_pwm_curve_registers' was not declared. Should it be static?
>> drivers/platform/x86/ayn-ec.c:753:18: sparse: sparse: symbol 'ayn_led_mc_subled_info' was not declared. Should it be static?
>> drivers/platform/x86/ayn-ec.c:774:24: sparse: sparse: symbol 'ayn_led_mc' was not declared. Should it be static?

vim +/ayn_led_mc_subled_info +753 drivers/platform/x86/ayn-ec.c

   752	
 > 753	struct mc_subled ayn_led_mc_subled_info[] = {
   754		{
   755			.color_index = LED_COLOR_ID_RED,
   756			.brightness = 0,
   757			.intensity = 0,
   758			.channel = AYN_LED_MC_RED_REG,
   759		},
   760		{
   761			.color_index = LED_COLOR_ID_GREEN,
   762			.brightness = 0,
   763			.intensity = 0,
   764			.channel = AYN_LED_MC_GREEN_REG,
   765		},
   766		{
   767			.color_index = LED_COLOR_ID_BLUE,
   768			.brightness = 0,
   769			.intensity = 0,
   770			.channel = AYN_LED_MC_BLUE_REG,
   771		},
   772	};
   773	
 > 774	struct led_classdev_mc ayn_led_mc = {
   775		.led_cdev = {
   776			.name = "ayn:rgb:joystick_rings",
   777			.brightness = 0,
   778			.max_brightness = 255,
   779			.brightness_set = ayn_led_mc_brightness_set,
   780			.brightness_get = ayn_led_mc_brightness_get,
   781			.color = LED_COLOR_ID_RGB,
   782		},
   783		.num_colors = ARRAY_SIZE(ayn_led_mc_subled_info),
   784		.subled_info = ayn_led_mc_subled_info,
   785	};
   786	

-- 
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

  parent reply	other threads:[~2025-07-28 23:37 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-26 20:40 [PATCH v3 0/4] Add AYN EC Platform Driver Derek J. Clark
2025-07-26 20:40 ` [PATCH v3 1/4] platform/x86: (ayn-ec) Add PWM Fan HWMON Interface Derek J. Clark
2025-07-26 23:32   ` Armin Wolf
2025-07-29  2:58     ` Derek John Clark
2025-07-29  4:09       ` Armin Wolf
2025-08-10 22:27         ` Derek John Clark
2025-08-11  8:38           ` Armin Wolf
2025-07-28 16:31   ` kernel test robot
2025-07-29  3:39     ` Randy Dunlap
2025-07-28 21:34   ` kernel test robot
2025-07-26 20:40 ` [PATCH v3 2/4] platform/x86: (ayn-ec) Add Temperature Sensors Derek J. Clark
2025-07-26 23:37   ` Armin Wolf
2025-07-29  3:02     ` Derek John Clark
2025-07-26 20:40 ` [PATCH v3 3/4] platform/x86: (ayn-ec) Add RGB Interface Derek J. Clark
2025-07-26 23:58   ` Armin Wolf
2025-07-29  3:25     ` Derek John Clark
2025-07-29  4:18       ` Armin Wolf
2025-07-28 23:36   ` kernel test robot [this message]
2025-07-26 20:40 ` [PATCH v3 4/4] platform/x86: (ayn-ec) Add AYN EC Platform Documentation Derek J. Clark
2025-07-27  0:03   ` Armin Wolf
2025-07-29  3:26     ` Derek John Clark

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=202507290730.7XZMyOM7-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=alok.a.tiwari@oracle.com \
    --cc=david.e.box@linux.intel.com \
    --cc=derekjohn.clark@gmail.com \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jdelvare@suse.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --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;
as well as URLs for NNTP newsgroup(s).