From: "Alexander Shiyan" <shc_work@mail.ru>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>
Cc: "Bryan Wu" <cooloney@gmail.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the leds tree
Date: Mon, 17 Jun 2013 10:26:31 +0400 [thread overview]
Message-ID: <1371450391.658890225@f333.mail.ru> (raw)
In-Reply-To: <20130617152908.1b9c999c01f18262a387dc91@canb.auug.org.au>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 849 bytes --]
> Hi Bryan,
>
> After merging the leds tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
>
> drivers/leds/leds-mc13783.c: In function 'mc13xxx_led_probe':
> drivers/leds/leds-mc13783.c:280:4: error: implicit declaration of function 'of_get_next_child' [-Werror=implicit-function-declaration]
> child = of_get_next_child(parent, child);
> ^
>
> Caused by commit 2ca3a455432f ("leds: leds-mc13783: Add devicetree support"). of_get_next_child() is only defined if CONFIG_OF is set.
>
> I have used the version of the leds tree from next-20130607 for today.
The patch has already been sent by me.
http://www.spinics.net/lists/linux-leds/msg00994.html
---
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2013-06-17 6:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-17 5:29 linux-next: build failure after merge of the leds tree Stephen Rothwell
2013-06-17 6:26 ` Alexander Shiyan [this message]
2013-06-21 0:16 ` Stephen Rothwell
2013-06-21 0:27 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2022-09-26 20:53 broonie
2022-09-26 21:18 ` Pavel Machek
2022-09-23 4:31 Stephen Rothwell
2020-01-06 3:21 Stephen Rothwell
2020-01-06 9:31 ` Guido Günther
2020-01-06 10:32 ` Pavel Machek
2020-01-06 15:52 ` Guido Günther
2019-07-25 2:31 Stephen Rothwell
2019-07-25 18:44 ` Jacek Anaszewski
2013-01-23 4:12 Stephen Rothwell
2013-01-23 6:05 ` Kim, Milo
2012-06-13 4:10 Stephen Rothwell
2012-06-13 4:25 ` Bryan Wu
2012-06-08 2:44 Stephen Rothwell
2012-06-08 3:33 ` Bryan Wu
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=1371450391.658890225@f333.mail.ru \
--to=shc_work@mail.ru \
--cc=cooloney@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).