All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>,
	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>
Subject: Re: linux-next: Tree for Jan 26 (gpu/drm/i915/)
Date: Mon, 29 Jan 2018 10:45:06 +0200	[thread overview]
Message-ID: <87o9ldkq99.fsf@intel.com> (raw)
In-Reply-To: <a44d975f-6514-c71c-e885-abf8764b93cd@infradead.org>

On Fri, 26 Jan 2018, Randy Dunlap <rdunlap@infradead.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.


BR,
Jani.


-- 
Jani Nikula, Intel Open Source Technology Center

  reply	other threads:[~2018-01-29  8:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-26  2:58 linux-next: Tree for Jan 26 Stephen Rothwell
2018-01-26 18:29 ` linux-next: Tree for Jan 26 (gpu/drm/i915/) Randy Dunlap
2018-01-29  8:45   ` Jani Nikula [this message]
2018-01-29 19:24     ` Randy Dunlap

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=87o9ldkq99.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.