From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux-kernel@vger.kernel.org,
linux-media <linux-media@vger.kernel.org>,
Sakari Ailus <sakari.ailus@iki.fi>
Subject: Re: linux-next: Tree for Apr 10 (media/i2c/adp1653)
Date: Fri, 10 Apr 2015 10:25:23 -0700 [thread overview]
Message-ID: <55280783.20405@infradead.org> (raw)
In-Reply-To: <5528071C.2040102@infradead.org>
[change email address for maintainer]
On 04/10/15 10:23, Randy Dunlap wrote:
> On 04/10/15 04:18, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20150409:
>>
>
> on i386:
>
> CC [M] drivers/media/i2c/adp1653.o
> ../drivers/media/i2c/adp1653.c: In function '__adp1653_set_power':
> ../drivers/media/i2c/adp1653.c:317:38: error: 'struct adp1653_platform_data' has no member named 'power_gpio'
> gpio_set_value(flash->platform_data->power_gpio, on);
> ^
> ../drivers/media/i2c/adp1653.c:336:38: error: 'struct adp1653_platform_data' has no member named 'power_gpio'
> gpio_set_value(flash->platform_data->power_gpio, 0);
> ^
> ../drivers/media/i2c/adp1653.c: In function 'adp1653_of_init':
> ../drivers/media/i2c/adp1653.c:471:4: error: 'struct adp1653_platform_data' has no member named 'power_gpio'
> pd->power_gpio = of_get_gpio_flags(node, 0, &flags);
> ^
> ../drivers/media/i2c/adp1653.c:472:8: error: 'struct adp1653_platform_data' has no member named 'power_gpio'
> if (pd->power_gpio < 0) {
> ^
> ../drivers/media/i2c/adp1653.c:433:6: warning: unused variable 'gpio' [-Wunused-variable]
> int gpio;
> ^
>
>
>
--
~Randy
next prev parent reply other threads:[~2015-04-10 17:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-10 11:18 linux-next: Tree for Apr 10 Stephen Rothwell
2015-04-10 17:06 ` linux-next: Tree for Apr 10 (media/i2c/ov2659) Randy Dunlap
2015-04-10 17:23 ` linux-next: Tree for Apr 10 (media/i2c/adp1653) Randy Dunlap
2015-04-10 17:25 ` Randy Dunlap [this message]
2015-04-10 19:57 ` Sakari Ailus
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=55280783.20405@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
--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).