From: Lee Jones <lee.jones@linaro.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Tomeu Vizoso <tomeu.vizoso@collabora.com>
Subject: Re: linux-next: build failure after merge of the backlight tree
Date: Wed, 27 May 2015 08:45:11 +0100 [thread overview]
Message-ID: <20150527074511.GR11677@x1> (raw)
In-Reply-To: <20150527131118.6e3ef667@canb.auug.org.au>
On Wed, 27 May 2015, Stephen Rothwell wrote:
> 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").
Yes, I need to remove that commit. Thanks for letting me know.
> I have used the backlight tree from next-20150526 for today.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2015-05-27 7:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 3:11 linux-next: build failure after merge of the backlight tree Stephen Rothwell
2015-05-27 7:45 ` Lee Jones [this message]
-- 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=20150527074511.GR11677@x1 \
--to=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=tomeu.vizoso@collabora.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 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.