linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Kanzenbach <kurt@linutronix.de>
To: kernel test robot <lkp@intel.com>
Cc: llvm@lists.linux.dev, 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: Re: [linux-next:master 6213/9575] igc_leds.c:undefined reference to `devm_led_classdev_register_ext'
Date: Sun, 25 Feb 2024 12:00:14 +0100	[thread overview]
Message-ID: <87sf1g7qrl.fsf@kurt.kurt.home> (raw)
In-Reply-To: <202402241123.p7RgyuiU-lkp@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1450 bytes --]

Hello,

On Sat Feb 24 2024, kernel test robot wrote:
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> head:   33e1d31873f87d119e5120b88cd350efa68ef276
> commit: ea578703b03d5d651b091c39f717dc829155b520 [6213/9575] igc: Add support for LEDs on i225/i226
> config: um-randconfig-001-20240223 (https://download.01.org/0day-ci/archive/20240224/202402241123.p7RgyuiU-lkp@intel.com/config)
> compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240224/202402241123.p7RgyuiU-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/202402241123.p7RgyuiU-lkp@intel.com/
>
> All errors (new ones prefixed by >>):
>
>    /usr/bin/ld: warning: .tmp_vmlinux.kallsyms1 has a LOAD segment with RWX permissions
>    /usr/bin/ld: drivers/net/ethernet/intel/igc/igc_leds.o: in function `igc_led_setup':
>>> igc_leds.c:(.text+0x173): undefined reference to `devm_led_classdev_register_ext'
>    clang-16: error: linker command failed with exit code 1 (use -v to see invocation)

This is fixed by:

 https://lore.kernel.org/netdev/20240222100324.453272-1-arnd@kernel.org/

Thanks,
Kurt

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

      reply	other threads:[~2024-02-25 11:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24  3:49 kernel test robot
2024-02-25 11:00 ` Kurt Kanzenbach [this message]

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=87sf1g7qrl.fsf@kurt.kurt.home \
    --to=kurt@linutronix.de \
    --cc=andrew@lunn.ch \
    --cc=anthony.l.nguyen@intel.com \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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