From: Sylwester Nawrocki <s.nawrocki@samsung.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media <linux-media@vger.kernel.org>,
Andrzej Hajda <a.hajda@samsung.com>
Subject: Re: linux-next: Tree for Apr 9 (media/i2c/s5c73m3)
Date: Wed, 09 Apr 2014 18:20:54 +0200 [thread overview]
Message-ID: <53457366.6000905@samsung.com> (raw)
In-Reply-To: <53456EDE.5000807@infradead.org>
Hi,
On 09/04/14 18:01, Randy Dunlap wrote:
> On 04/09/2014 12:22 AM, Stephen Rothwell wrote:
>> > Hi all,
>> >
>> > Please do not add material intended for v3.16 to your linux-next included
>> > branches until after v3.15-rc1 is released.
>> >
>> > This tree still fails (more than usual) the powerpc allyesconfig build.
>> >
>> > Changes since 20140408:
>> >
> on i386:
> CONFIG_OF is not enabled.
>
> drivers/media/i2c/s5c73m3/s5c73m3-core.c: In function 's5c73m3_get_platform_data':
> drivers/media/i2c/s5c73m3/s5c73m3-core.c:1619:2: error: implicit declaration of function 'v4l2_of_get_next_endpoint' [-Werror=implicit-function-declaration]
> drivers/media/i2c/s5c73m3/s5c73m3-core.c:1619:10: warning: assignment makes pointer from integer without a cast [enabled by default]
I have already prepared a patch for this issue:
https://patchwork.linuxtv.org/patch/23465
--
Thanks,
Sylwester
prev parent reply other threads:[~2014-04-09 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-09 7:22 linux-next: Tree for Apr 9 Stephen Rothwell
2014-04-09 16:01 ` linux-next: Tree for Apr 9 (media/i2c/s5c73m3) Randy Dunlap
2014-04-09 16:20 ` Sylwester Nawrocki [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=53457366.6000905@samsung.com \
--to=s.nawrocki@samsung.com \
--cc=a.hajda@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@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 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).