From: kernel test robot <lkp@intel.com>
To: Joseph Strauss <jstrauss@mailbox.org>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Lee Jones <lee@kernel.org>
Subject: [linux-next:master 2040/3984] drivers/leds/leds-blinkm.c:440:undefined reference to `led_mc_calc_color_components'
Date: Sun, 11 Aug 2024 17:23:46 +0800 [thread overview]
Message-ID: <202408111700.OhOvZxD1-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 61c01d2e181adfba02fe09764f9fca1de2be0dbe
commit: 56e8c56c9af0df8b6de7bc4b6d9a2f4570b055db [2040/3984] leds: Add multicolor support to BlinkM LED driver
config: m68k-randconfig-r064-20240811 (https://download.01.org/0day-ci/archive/20240811/202408111700.OhOvZxD1-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 14.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240811/202408111700.OhOvZxD1-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/202408111700.OhOvZxD1-lkp@intel.com/
All errors (new ones prefixed by >>):
m68k-linux-ld: drivers/leds/leds-blinkm.o: in function `blinkm_set_mc_brightness':
>> drivers/leds/leds-blinkm.c:440:(.text+0x4b2): undefined reference to `led_mc_calc_color_components'
m68k-linux-ld: drivers/leds/leds-blinkm.o: in function `blinkm_probe':
>> include/linux/led-class-multicolor.h:70:(.text+0x740): undefined reference to `led_classdev_multicolor_register_ext'
vim +440 drivers/leds/leds-blinkm.c
432
433 static int blinkm_set_mc_brightness(struct led_classdev *led_cdev,
434 enum led_brightness value)
435 {
436 struct led_classdev_mc *mcled_cdev = lcdev_to_mccdev(led_cdev);
437 struct blinkm_led *led = mcled_cdev_to_led(mcled_cdev);
438 struct blinkm_data *data = i2c_get_clientdata(led->i2c_client);
439
> 440 led_mc_calc_color_components(mcled_cdev, value);
441
442 data->next_red = (u8) mcled_cdev->subled_info[RED].brightness;
443 data->next_green = (u8) mcled_cdev->subled_info[GREEN].brightness;
444 data->next_blue = (u8) mcled_cdev->subled_info[BLUE].brightness;
445
446 blinkm_transfer_hw(led->i2c_client, BLM_GO_RGB);
447
448 return 0;
449 }
450
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-11 9:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202408111700.OhOvZxD1-lkp@intel.com \
--to=lkp@intel.com \
--cc=jstrauss@mailbox.org \
--cc=lee@kernel.org \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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