From: Plamen Petrov <plamen.petrov@fs.ru.acad.bg>
To: Ivo van Doorn <ivdoorn@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: latest git (linux-2.6.25-git6) compile error
Date: Fri, 25 Apr 2008 09:02:15 +0300 [thread overview]
Message-ID: <481173E7.3050903@fs.ru.acad.bg> (raw)
In-Reply-To: <200804250107.40778.IvDoorn@gmail.com>
Ivo van Doorn wrote:
> On Thursday 24 April 2008, Plamen Petrov wrote:
>
>> Hi, folks!
>>
>> Just "git pulled" 2.6.25-git6, did the
>> "zcat /proc/config.gz > .config && make oldconfig" stuff,
>> and when I was asked for leds support (RT61PCI_LEDS)
>> in the RT61 driver I happen to use, got this:
>>
>> [***************** SNIP *********************]
>> LD net/built-in.o
>> LD vmlinux.o
>> MODPOST vmlinux.o
>> WARNING: modpost: Found 16 section mismatch(es).
>> To see full details build your kernel with:
>> 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>> GEN .version
>> CHK include/linux/compile.h
>> UPD include/linux/compile.h
>> CC init/version.o
>> LD init/built-in.o
>> LD .tmp_vmlinux1
>> drivers/built-in.o: In function `rt2x00leds_resume':
>> /tmp/compile/linux-2.6/drivers/net/wireless/rt2x00/rt2x00leds.c:216: undefined
>> reference to `led_classdev_resume'
>>
>
> Can you confirm that this error goes away when enabling CONFIG_NEW_LEDS ?
>
> Ivo
>
Will try and report later - now I'm at work, away from the machine.
Thanks,
--
Plamen Petrov, network & system administrator
Filial - Silistra
RU "Angel Kantchev"
http://fs.ru.acad.bg/
--------------------------------
this message is UTF8 encoded
next prev parent reply other threads:[~2008-04-25 6:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-24 21:28 Plamen Petrov
2008-04-24 23:07 ` Ivo van Doorn
2008-04-25 6:02 ` Plamen Petrov [this message]
2008-04-25 6:35 ` David Miller
2008-04-25 18:20 ` Ivo van Doorn
2008-04-26 16:06 ` plamen.petrov
2008-04-26 21:35 ` Mirco Tischler
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=481173E7.3050903@fs.ru.acad.bg \
--to=plamen.petrov@fs.ru.acad.bg \
--cc=ivdoorn@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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®