Re: [drm:drm-next 139/301] ERROR: "backlight_force_update" [drivers/gpu/drm/radeon/radeon.ko] undefined!

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, Oct 4, 2012 at 8:34 AM, Luca Tettamanti <kronos.it@xxxxxxxxx> wrote:
> On Thu, Oct 4, 2012 at 6:51 AM, Fengguang Wu <fengguang.wu@xxxxxxxxx> wrote:
>> Hi Luca,
>>
>> FYI, kernel build failed on
>>
>> tree:   git://people.freedesktop.org/~airlied/linux.git drm-next
>> head:   268d28371cd326be4dfcd7eba5917bf4b9d30c8f
>> commit: fda4b25c55a59ba12378e4b9e4553f6ea57d802d [139/301] drm/radeon: implement handler for ACPI event
>> config: ia64-defconfig
>>
>> All error/warnings:
>>
>> ERROR: "atombios_set_panel_brightness" [drivers/gpu/drm/radeon/radeon.ko] undefined!
>> ERROR: "backlight_force_update" [drivers/gpu/drm/radeon/radeon.ko] undefined!
>
> I'm not sure how to deal with this. The cause for both is that
> BACKLIGHT_CLASS_DEVICE is not enabled: backlight_force_update is
> easily fixed, atombios_set_panel_brightness however is removed in
> following patches.
> Should I send a patch against drm-next for backlight_force_update (and
> leave bisecting broken without BACKLIGHT_CLASS_DEVICE) or is it
> possible to amend this commit before it's merged by Linus?

It's already been merged.  I sent a fix out this morning:
http://lists.freedesktop.org/archives/dri-devel/2012-October/028546.html

Alex
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Development]     [Kernel Announce]     [Kernel Newbies]     [Linux Networking Development]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Device Mapper]

  Powered by Linux