From: Liam Girdwood <lg@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, Russell King <rmk@arm.linux.org.uk>,
Philipp Zabel <philipp.zabel@gmail.com>
Subject: Re: linux-next: voltage tree build failure
Date: Mon, 14 Jul 2008 14:48:56 +0100 [thread overview]
Message-ID: <1216043336.27680.63.camel@localhost.localdomain> (raw)
In-Reply-To: <20080714233530.f0edf140.sfr@canb.auug.org.au>
On Mon, 2008-07-14 at 23:35 +1000, Stephen Rothwell wrote:
> Hi Liam,
>
> Today's linux-next build (arm versatile_defconfig) failed like this:
>
> drivers/regulator/Kconfig:59: can't open file "drivers/regulator/wm8350/Kconfig"
>
> Commit 03ec18c8752a9b12006ffff23a5582b4482073ce ("regulator: TI bq24022
> Li-Ion Charger driver") added some includes to drivers/regulator/Kconfig
> of things that don't exist ...
>
> Unfortunately, this broke all arm builds.
Philipp noticed earlier and it's now fixed. It's stuff that does exist
on my system so I should probably git clean -f -d next time I build
(before commit).
Thanks
Liam
next prev parent reply other threads:[~2008-07-14 13:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-14 13:35 linux-next: voltage tree build failure Stephen Rothwell
2008-07-14 13:48 ` Liam Girdwood [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-01-21 2:46 Stephen Rothwell
2009-01-21 14:04 ` Jonathan Cameron
2009-04-28 6:24 Stephen Rothwell
2009-04-28 11:08 ` Liam Girdwood
2009-04-28 11:42 ` Stephen Rothwell
2009-04-30 11:06 ` Mike Rapoport
2009-08-24 4:40 Stephen Rothwell
2009-10-12 2:26 Stephen Rothwell
2009-10-12 2:50 ` Haojian Zhuang
2009-10-12 12:57 ` Mark Brown
2009-10-12 13:35 ` Samuel Ortiz
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=1216043336.27680.63.camel@localhost.localdomain \
--to=lg@opensource.wolfsonmicro.com \
--cc=linux-next@vger.kernel.org \
--cc=philipp.zabel@gmail.com \
--cc=rmk@arm.linux.org.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;
as well as URLs for NNTP newsgroup(s).