From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the voltage tree
Date: Thu, 11 Nov 2010 11:46:45 +0000 [thread overview]
Message-ID: <20101111114644.GC6052@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <20101111113638.eb3101d0.sfr@canb.auug.org.au>
On Thu, Nov 11, 2010 at 11:36:38AM +1100, Stephen Rothwell wrote:
> After merging the voltage tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
Oh, a platform where pcap can actually be built! That's useful, thanks.
> drivers/regulator/pcap-regulator.c:155: error: expected declaration specifiers or '...' before 'unsiged'
> drivers/regulator/pcap-regulator.c: In function 'pcap_regulator_set_voltage':
> drivers/regulator/pcap-regulator.c:175: error: 'selector' undeclared (first use in this function)
> drivers/regulator/pcap-regulator.c: At top level:
> drivers/regulator/pcap-regulator.c:251: warning: initialization from incompatible pointer type
> Caused by commit d2f03ebfe8c63d1e3e1ab2352dd32d161546003e ("regulator:
> Report actual configured voltage to set_voltage()"). Please always build
> changed files ...
With a lot of the embedded drivers that can be difficult - often there
are dependencies on APIs that are only available on a small set of
platforms (which may not even be documented). For example, with PCAP
the core driver uses irq_to_gpio() which is not implemented on any of
the platforms I commonly build for.
next prev parent reply other threads:[~2010-11-11 11:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-11 0:36 linux-next: build failure after merge of the voltage tree Stephen Rothwell
2010-11-11 11:46 ` Mark Brown [this message]
2010-11-11 12:09 ` Liam Girdwood
-- strict thread matches above, loose matches on Subject: below --
2010-12-14 4:49 Stephen Rothwell
2010-12-14 5:10 ` Yong Shen
2010-12-14 15:56 ` Liam Girdwood
2010-12-15 2:03 ` Yong Shen
2010-12-15 2:09 Stephen Rothwell
2010-12-15 9:04 ` Liam Girdwood
2010-12-15 14:03 ` Mark Brown
2011-05-10 2:44 Stephen Rothwell
2011-05-10 8:38 ` Liam Girdwood
2011-05-10 17:30 ` Jorge Eduardo Candelaria
2011-05-10 19:57 ` Liam Girdwood
2011-05-11 2:27 ` Stephen Rothwell
2011-05-11 6:43 ` Jorge Eduardo Candelaria
2011-05-11 13:29 ` Liam Girdwood
[not found] <201105271759.p4RHxa2X008919@hera.kernel.org>
2011-05-27 19:58 ` Randy Dunlap
2011-05-27 21:13 ` Liam Girdwood
2011-05-27 21:21 ` Randy Dunlap
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=20101111114644.GC6052@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@slimlogic.co.uk \
--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