From: Lee <lee-in-berlin@web.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG] 2.6.30-rc4: compile fail with CONFIG_DRM_I915=y
Date: Sun, 03 May 2009 11:39:00 +0200 [thread overview]
Message-ID: <49FD6634.1080602@web.de> (raw)
In-Reply-To: <49FC7A13.8040807@oracle.com>
Randy Dunlap wrote:
> Lee wrote:
>> Hi list,
>>
>> compiling 2.6.30-rc4 with following options will result in an compile
>> error:
>>
>> CONFIG_DRM_I915=y
>> CONFIG_ACPI_VIDEO=m
>>
>>
>> drivers/video/backlight/backlight.c: In function
>> ‘backlight_device_register’:
>> drivers/video/backlight/backlight.c:247: warning: format not a string
>> literal and no format arguments
>> drivers/video/output.c: In function ‘video_output_register’:
>> drivers/video/output.c:99: warning: format not a string literal and no
>> format arguments
>> drivers/usb/storage/libusual.c: In function ‘usu_probe_thread’:
>> drivers/usb/storage/libusual.c:159: warning: format not a string literal
>> and no format arguments
>> drivers/built-in.o: In function `intel_opregion_free':
>> (.text+0xaf051): undefined reference to `acpi_video_exit'
>> drivers/built-in.o: In function `intel_opregion_init':
>> (.text+0xaf411): undefined reference to `acpi_video_register'
>> make[1]: *** [.tmp_vmlinux1] Error 1
>> make[1]: Leaving directory `/home/randall/kernel-source'
>> make: *** [debian/stamp/build/kernel] Error 2
>>
>> Compiling the kernel with both options as module or both options
>> built-in results in a working kernel.
>
> Len Brown posted a patch to fix this, although I can't find it in
> any email archives just now, so I'm appending it below.
>
>
Thanks! I'll keep an eye on it that it's merged for the next rc.
prev parent reply other threads:[~2009-05-03 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 13:50 [BUG] 2.6.30-rc4: compile fail with CONFIG_DRM_I915=y Lee
2009-05-02 16:51 ` Randy Dunlap
2009-05-03 9:39 ` Lee [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=49FD6634.1080602@web.de \
--to=lee-in-berlin@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.