From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Dec 18 (drm/i915/display/intel_panel)
Date: Fri, 18 Dec 2020 09:19:10 -0800 [thread overview]
Message-ID: <a4e33500-07b0-c402-2eb7-d3ebad78c195@infradead.org> (raw)
In-Reply-To: <20201218163344.2734c78d@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On 12/17/20 9:33 PM, Stephen Rothwell wrote:
> Hi all,
>
> News: there will be no linux-next releases between Dec 24 and Jan
> 3 inclusive.
>
> Please do not add any v5.12 destined code to your linux-next included
> branches until after v5.11-rc1 has been released.
>
> Changes since 20201217:
>
on i386:
ld: drivers/gpu/drm/i915/display/intel_panel.o: in function `intel_backlight_device_register':
intel_panel.c:(.text+0x2f4f): 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+0x2fc8): undefined reference to `backlight_device_unregister'
CONFIG_BACKLIGHT_CLASS_DEVICE=m
CONFIG_DRM_I915=y
Full randconfig file is attached.
--
~Randy
Reported-by: Randy Dunlap <rdunlap@infradead.org>
[-- Attachment #2: config-r6825.xz --]
[-- Type: application/x-xz, Size: 27404 bytes --]
prev parent reply other threads:[~2020-12-18 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 5:33 linux-next: Tree for Dec 18 Stephen Rothwell
2020-12-18 17:19 ` 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=a4e33500-07b0-c402-2eb7-d3ebad78c195@infradead.org \
--to=rdunlap@infradead.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®