public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Lee Jones <lee.jones@linaro•org>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Tomeu Vizoso <tomeu.vizoso@collabora•com>
Subject: linux-next: build failure after merge of the backlight tree
Date: Wed, 27 May 2015 13:11:18 +1000	[thread overview]
Message-ID: <20150527131118.6e3ef667@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 612 bytes --]

Hi Lee,

After merging the backlight tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:

drivers/video/backlight/backlight.c: In function 'of_find_backlight_by_node':
drivers/video/backlight/backlight.c:563:2: error: implicit declaration of function 'of_platform_device_ensure' [-Werror=implicit-function-declaration]
  of_platform_device_ensure(node);
  ^

Caused by commit 67a6b10546ea ("backlight: Probe backlight devices on
demand").

I have used the backlight tree from next-20150526 for today.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-05-27  3:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27  3:11 Stephen Rothwell [this message]
2015-05-27  7:45 ` linux-next: build failure after merge of the backlight tree Lee Jones
  -- strict thread matches above, loose matches on Subject: below --
2024-02-26  2:28 Stephen Rothwell
2024-03-05  0:16 ` Stephen Rothwell
2024-03-05  9:17   ` Lee Jones
2024-03-05 22:55     ` Stephen Rothwell
2024-03-06  3:04       ` Stephen Rothwell
2024-03-07  8:24         ` Lee Jones
2024-03-07  9:04           ` Lee Jones
2024-03-07 19:30             ` Stephen Rothwell
2010-05-10  2:43 Stephen Rothwell
2010-05-10  5:41 ` Mike Frysinger
2010-05-17  3:32 ` Stephen Rothwell
2010-05-18 15:54   ` Richard Purdie
2010-05-19  0:56     ` 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=20150527131118.6e3ef667@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=lee.jones@linaro$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=tomeu.vizoso@collabora$(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