linux-kernel - [build bug] drivers/built-in.o: In function `rt2x00leds_resume': : undefined reference to `led_classdev

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 20 Apr 2008 10:13:02 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	David Miller <davem@...emloft.net>,
	"John W. Linville" <linville@...driver.com>,
	Tomas Winkler <tomas.winkler@...el.com>
Cc:	linux-kernel@...r.kernel.org, kaber@...sh.net,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	netdev@...r.kernel.org, netfilter-devel@...r.kernel.org,
	Mohamed Abbas <mabbas@...ux.intel.com>,
	Ian Schram <ischram@...enet.be>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Ivo van Doorn <ivdoorn@...il.com>
Subject: [build bug] drivers/built-in.o: In function `rt2x00leds_resume': :
	undefined reference to `led_classdev_resume'

* Ingo Molnar <mingo@...e.hu> wrote:

> a third -git build failure triggered in last night's x86.git 
> build/boot testing:

and after i restarted last night's QA run, within a few iterations a 
fourth build failure popped up:

  drivers/built-in.o: In function `rt2x00leds_resume':
  : undefined reference to `led_classdev_resume'
  drivers/built-in.o: In function `rt2x00leds_resume':
  : undefined reference to `led_classdev_resume'
  [...]

config:

  http://redhat.com/~mingo/misc/config-Sun_Apr_20_09_43_01_CEST_2008.bad

suspected commit is: a2e1d52a32 "rt2x00: Remove MAC80211_LEDS 
dependency".

so far the -git track record: 4 networking build failures 1 SCSI build 
failure. (and i'm not picking these bugs nor am i trying to pick any 
fight here - randconfig does)

... and i think a little bit of grumpiness might be in order now: none 
of these commits were announced on lkml, so i have to hijack this thread 
again. As exciting as reporting bugs might seem from the outside, i'm 
supposed to find x86 and scheduler bugs, not networking bugs. Really, 
your practice of removing networking commits and pull requests from lkml 
does not result in a stellar quality track record.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/