From: Randy Dunlap <rdunlap@infradead.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: linux-next: Tree for Jan 23 (gpu/drm/panel/)
Date: Thu, 23 Jan 2020 15:46:59 -0800 [thread overview]
Message-ID: <6a610bdf-3227-fcad-6208-e1e7e085c940@infradead.org> (raw)
In-Reply-To: <20200123194959.GA25073@ravnborg.org>
On 1/23/20 11:49 AM, Sam Ravnborg wrote:
> Hi Randy.
>
> Thanks - I think (kidding, this has bugged of for a long time).
>
> On Thu, Jan 23, 2020 at 12:44:25AM -0800, Randy Dunlap wrote:
>> On 1/22/20 10:21 PM, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> Changes since 20200122:
>>>
>>
>>
>> on i386:
>>
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-sharp-lq101r1sx01.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-rocktech-jh057n00900.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-raydium-rm68200.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-panasonic-vvx10f034n00.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-osd-osd101t2587-53ts.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-olimex-lcd-olinuxino.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-leadtek-ltk500hd1829.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-kingdisplay-kd097d04.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-innolux-p079zca.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-ilitek-ili9881c.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-lvds.ko] undefined!
>> ERROR: "drm_panel_of_backlight" [drivers/gpu/drm/panel/panel-boe-himax8279d.ko]
>>
>>
>> Full randconfig file is attached.
>
> I tried reproducing with latest drm-misc-next - no luck.
>
> Can you check if you have:
>
> 8d6cb2f7fb90018d9e3efdc9bc95e6da213a352f
> drm/drm_panel: fix export of drm_panel_of_backlight, try #3
>
>
> As we expect this to fix it for good.
> Maybe the patch has not hit the right tree
> and is thus not in -next.
Hi Sam,
Sorry, I don't have the linux-next git tree so I can't check that commit.
--
~Randy
next prev parent reply other threads:[~2020-01-23 23:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 6:21 linux-next: Tree for Jan 23 Stephen Rothwell
2020-01-23 7:00 ` linux-next: Tree for Jan 23 (PHY_EXYNOS5250_SATA in drivers/phy/samsung/Kconfig) Randy Dunlap
2020-01-23 8:03 ` Krzysztof Kozlowski
2020-01-23 8:59 ` Randy Dunlap
2020-01-23 9:09 ` Wolfram Sang
2020-01-23 8:44 ` linux-next: Tree for Jan 23 (gpu/drm/panel/) Randy Dunlap
2020-01-23 19:49 ` Sam Ravnborg
2020-01-23 23:46 ` Randy Dunlap [this message]
2020-01-24 0:16 ` Stephen Rothwell
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=6a610bdf-3227-fcad-6208-e1e7e085c940@infradead.org \
--to=rdunlap@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=sfr@canb.auug.org.au \
--cc=thierry.reding@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).