From: Randy Dunlap <randy.dunlap@oracle•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>, Zhang Rui <rui.zhang@intel•com>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
linux-acpi@vger•kernel.org
Subject: Re: linux-next: Tree for November 9 (acpi_video)
Date: Tue, 9 Nov 2010 17:06:21 -0800 [thread overview]
Message-ID: <20101109170621.32db3873.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20101109151618.a562f77a.sfr@canb.auug.org.au>
On Tue, 9 Nov 2010 15:16:18 +1100 Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20101029:
one build had these errors:
drivers/built-in.o: In function `acpi_video_bus_put_one_device':
video.c:(.text+0x59bee): undefined reference to `thermal_cooling_device_unregister'
video.c:(.text+0x59bff): undefined reference to `video_output_unregister'
drivers/built-in.o: In function `acpi_video_device_find_cap':
video.c:(.text+0x5b3fc): undefined reference to `thermal_cooling_device_register'
video.c:(.text+0x5b57b): undefined reference to `video_output_register'
and another one had these errors:
drivers/built-in.o: In function `acpi_video_bus_put_one_device':
video.c:(.text+0xdc14a): undefined reference to `backlight_device_unregister'
drivers/built-in.o: In function `acpi_video_switch_brightness':
video.c:(.text+0xdc821): undefined reference to `backlight_force_update'
drivers/built-in.o: In function `acpi_video_device_find_cap':
video.c:(.text+0xdd8bd): undefined reference to `backlight_device_register'
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
prev parent reply other threads:[~2010-11-10 1:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-09 4:16 linux-next: Tree for November 9 Stephen Rothwell
2010-11-10 1:06 ` Randy Dunlap [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=20101109170621.32db3873.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle$(echo .)com \
--cc=linux-acpi@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rui.zhang@intel$(echo .)com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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