From: Jonathan Cameron <jic23@cam.ac.uk>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@slimlogic.co.uk>, linux-next@vger.kernel.org
Subject: Re: linux-next: voltage tree build failure
Date: Wed, 21 Jan 2009 14:04:48 +0000 [thread overview]
Message-ID: <49772B80.4090702@cam.ac.uk> (raw)
In-Reply-To: <20090121134600.d6e60b2f.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Liam,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/regulator/wm8350-regulator.c: In function 'pmic_uv_handler':
> drivers/regulator/wm8350-regulator.c:1296: error: dereferencing pointer to incomplete type
> drivers/regulator/wm8350-regulator.c:1305: error: dereferencing pointer to incomplete type
>
> Immediate cause is commit 872ed3fe176833f7d43748eb88010da4bbd2f983
> ("Regulator: Push lock out of _notifier_call_chain + add voltage change
> event").
>
> I have dropped the voltage tree for today.
Sorry, my error... It's always the simple changes that you don't build
test properly that catch you out.
Liam, can you revert this patch for now and I'll send a version
that doesn't have this problem shortly.
Jonathan
next prev parent reply other threads:[~2009-01-21 14:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 2:46 linux-next: voltage tree build failure Stephen Rothwell
2009-01-21 14:04 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2009-08-24 4:40 Stephen Rothwell
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
2008-07-14 13:35 Stephen Rothwell
2008-07-14 13:48 ` Liam Girdwood
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=49772B80.4090702@cam.ac.uk \
--to=jic23@cam.ac.uk \
--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;
as well as URLs for NNTP newsgroup(s).