From: Sam Ravnborg <sam@ravnborg•org>
To: Randy Dunlap <rdunlap@infradead•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>,
Thierry Reding <thierry.reding@gmail•com>,
dri-devel <dri-devel@lists•freedesktop.org>,
intel-gfx <intel-gfx@lists•freedesktop.org>
Subject: Re: linux-next: Tree for Dec 16 (drm_panel & intel_panel)
Date: Tue, 17 Dec 2019 06:42:55 +0100 [thread overview]
Message-ID: <20191217054255.GA26868@ravnborg.org> (raw)
In-Reply-To: <d92bec2a-62cb-004e-7f8c-01fc12a53a74@infradead.org>
Hi Randy.
On Mon, Dec 16, 2019 at 08:25:11AM -0800, Randy Dunlap wrote:
> On 12/15/19 9:22 PM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20191213:
> >
>
> on x86_64:
>
> ld: drivers/gpu/drm/drm_panel.o: in function `drm_panel_of_backlight':
> (.text+0x2ee): undefined reference to `devm_of_find_backlight'
>
> ld: drivers/gpu/drm/i915/display/intel_panel.o: in function `intel_backlight_device_register':
> intel_panel.c:(.text+0x593e): undefined reference to `backlight_device_register'
> ld: drivers/gpu/drm/i915/display/intel_panel.o: in function `intel_backlight_device_unregister':
> intel_panel.c:(.text+0x5a04): undefined reference to `backlight_device_unregister'
>
> CONFIG_DRM_PANEL=y
> CONFIG_BACKLIGHT_CLASS_DEVICE=m
> CONFIG_DRM_I915=y
>
> Full randconfig file is attached.
Can you please verify if you have:
907aa265fde6589b8059dc51649c6d1f49ade2f3
("drm/drm_panel: fix EXPORT of drm_panel_of_backlight")
This commit is supposed to fix it.
Sam
next prev parent reply other threads:[~2019-12-17 5:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 5:22 linux-next: Tree for Dec 16 Stephen Rothwell
2019-12-16 16:25 ` linux-next: Tree for Dec 16 (drm_panel & intel_panel) Randy Dunlap
2019-12-17 5:42 ` Sam Ravnborg [this message]
2019-12-17 6:37 ` Randy Dunlap
2019-12-17 11:52 ` Steven Price
2019-12-17 14:02 ` Andy Shevchenko
2019-12-17 15:28 ` [Intel-gfx] " Jani Nikula
2019-12-17 15:49 ` Andy Shevchenko
2019-12-17 16:06 ` Jani Nikula
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=20191217054255.GA26868@ravnborg.org \
--to=sam@ravnborg$(echo .)org \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rdunlap@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=thierry.reding@gmail$(echo .)com \
/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