From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@davemloft.net>,
Ivo van Doorn <ivdoorn@gmail.com>
Subject: Re: [patch/bugreport] rt2x00: build fix
Date: Sat, 3 May 2008 19:47:54 +0300 [thread overview]
Message-ID: <20080503164754.GL5838@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <20080503124711.GA18244@elte.hu>
On Sat, May 03, 2008 at 02:47:11PM +0200, Ingo Molnar wrote:
>
> x86.git testing found the following build failure on latest -git:
>
> Building modules, stage 2.
> MODPOST 332 modules
> ERROR: "led_classdev_unregister" [drivers/net/wireless/rt2x00/rt2x00lib.ko] undefined!
> ERROR: "led_classdev_resume" [drivers/net/wireless/rt2x00/rt2x00lib.ko] undefined!
> ERROR: "led_classdev_register" [drivers/net/wireless/rt2x00/rt2x00lib.ko] undefined!
> ERROR: "led_classdev_suspend" [drivers/net/wireless/rt2x00/rt2x00lib.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> config can be found at:
>
> http://redhat.com/~mingo/misc/config-Sat_May__3_13_24_19_CEST_2008.bad
>
> the patch here is just a quick workaround for now for my test-setup, it
> makes the leds features in this driver depend on NEW_LEDS. Have not
> checked how far away this is from the real fix. Hm, and i think think i
> sent another patch for a similar build failure a week ago already - did
> i miss some patch to try?
You missed Roman's patch two days ago, that was in response to a similar
report you sent, and that will also fix this issue.
> Ingo
>...
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
prev parent reply other threads:[~2008-05-03 16:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 12:47 Ingo Molnar
2008-05-03 13:19 ` Ivo van Doorn
2008-05-03 16:47 ` Adrian Bunk [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=20080503164754.GL5838@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=davem@davemloft.net \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®