linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: oe-kbuild-all@lists.linux.dev,
	Linux Memory Management List <linux-mm@kvack.org>,
	Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
	Tony Nguyen <anthony.l.nguyen@intel.com>
Subject: [linux-next:master 5947/10830] include/linux/leds.h:299:(.text.igc_led_setup+0x170): undefined reference to `devm_led_classdev_register_ext'
Date: Thu, 29 Feb 2024 04:32:16 +0800	[thread overview]
Message-ID: <202402290415.zUrgBrwr-lkp@intel.com> (raw)

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head:   20af1ca418d2c0b11bc2a1fe8c0c88f67bcc2a7e
commit: ea578703b03d5d651b091c39f717dc829155b520 [5947/10830] igc: Add support for LEDs on i225/i226
config: powerpc-randconfig-r004-20230504 (https://download.01.org/0day-ci/archive/20240229/202402290415.zUrgBrwr-lkp@intel.com/config)
compiler: powerpc-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240229/202402290415.zUrgBrwr-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/202402290415.zUrgBrwr-lkp@intel.com/

All errors (new ones prefixed by >>):

   powerpc-linux-ld: drivers/net/ethernet/intel/igc/igc_leds.o: in function `devm_led_classdev_register':
>> include/linux/leds.h:299:(.text.igc_led_setup+0x170): undefined reference to `devm_led_classdev_register_ext'


vim +299 include/linux/leds.h

7c322056e3564d Jacek Anaszewski 2019-08-26  295  
7c322056e3564d Jacek Anaszewski 2019-08-26  296  static inline int devm_led_classdev_register(struct device *parent,
7c322056e3564d Jacek Anaszewski 2019-08-26  297  					     struct led_classdev *led_cdev)
7c322056e3564d Jacek Anaszewski 2019-08-26  298  {
7c322056e3564d Jacek Anaszewski 2019-08-26 @299  	return devm_led_classdev_register_ext(parent, led_cdev, NULL);
7c322056e3564d Jacek Anaszewski 2019-08-26  300  }
ec28a8cfdce630 Dan Murphy       2019-10-02  301  void led_classdev_unregister(struct led_classdev *led_cdev);
ec28a8cfdce630 Dan Murphy       2019-10-02  302  void devm_led_classdev_unregister(struct device *parent,
ca1bb4ee4c3a01 Bjorn Andersson  2015-02-23  303  				  struct led_classdev *led_cdev);
ec28a8cfdce630 Dan Murphy       2019-10-02  304  void led_classdev_suspend(struct led_classdev *led_cdev);
ec28a8cfdce630 Dan Murphy       2019-10-02  305  void led_classdev_resume(struct led_classdev *led_cdev);
c72a1d608dd0eb Richard Purdie   2006-03-31  306  

:::::: The code at line 299 was first introduced by commit
:::::: 7c322056e3564da1b5bdc3f3cb79229582955eb2 leds: Replace {devm_}led_classdev_register() macros with inlines

:::::: TO: Jacek Anaszewski <jacek.anaszewski@gmail.com>
:::::: CC: Jacek Anaszewski <jacek.anaszewski@gmail.com>

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


                 reply	other threads:[~2024-02-28 20:32 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=202402290415.zUrgBrwr-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=kurt@linutronix.de \
    --cc=linux-mm@kvack.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=pabeni@redhat.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