linux-kernel - Re: linux-next: Tree for Jan 26 (gpu/drm/i915/)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <e0e28fcd-8e65-b7b8-7fcf-c95a680b11f4@infradead.org>
Date:   Mon, 29 Jan 2018 11:24:25 -0800
From:   Randy Dunlap <rdunlap@...radead.org>
To:     Jani Nikula <jani.nikula@...ux.intel.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        dri-devel <dri-devel@...ts.freedesktop.org>
Subject: Re: linux-next: Tree for Jan 26 (gpu/drm/i915/)

On 01/29/2018 12:45 AM, Jani Nikula wrote:
> On Fri, 26 Jan 2018, Randy Dunlap <rdunlap@...radead.org> wrote:
>> On 01/25/2018 06:58 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20180119:
>>>
>>
>> on x86_64:
>> drivers/gpu/drm/i915/intel_panel.o: In function `intel_backlight_device_register':
>> intel_panel.c:(.text+0x28d4): undefined reference to `backlight_device_register'
>> drivers/gpu/drm/i915/intel_panel.o: In function `intel_backlight_device_unregister':
>> intel_panel.c:(.text+0x2991): undefined reference to `backlight_device_unregister'
>>
>> when CONFIG_BACKLIGHT_CLASS_DEVICE=m
>> and CONFIG_DRM_I915=y
> 
> I don't deny there's an issue with i915 selecting
> CONFIG_BACKLIGHT_CLASS_DEVICE. I'm afraid previous attempts at fixing
> that have been a rabbit hole; new config errors pop up
> elsewhere. [citation needed].
> 
> That said, I thought we had enough duct tape in the Kconfig to keep the
> issues at bay. Since you're replying to linux-next, are you saying this
> is new? I wonder if something's changed elsewhere.

Hi Jani,
I don't know that it's new. It just popped up in a linux-next randconfig build.

I'll look at the config dependencies a bit, but I do recall the rabbit hole
and I don't want to look or go there.

The randconfig file is attached if you are interested in checking it.

thanks,
-- 
~Randy

View attachment "config-r5172" of type "text/plain" (119747 bytes)