From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Liam Girdwood <lrg@ti.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Thomas Abraham <thomas.abraham@linaro.org>
Subject: Re: linux-next: build failure after merge of the final tree (regulator tree related)
Date: Tue, 17 Apr 2012 14:55:16 +0100 [thread overview]
Message-ID: <20120417135516.GF6652@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20120417142748.d42daa09958086a6e2ab4878@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Tue, Apr 17, 2012 at 02:27:48PM +1000, Stephen Rothwell wrote:
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> drivers/misc/max8997-muic.c: In function 'max8997_muic_irq_work':
> drivers/misc/max8997-muic.c:313:34: error: 'struct max8997_platform_data' has no member named 'irq_base'
> drivers/misc/max8997-muic.c: In function 'max8997_muic_probe':
> drivers/misc/max8997-muic.c:434:35: error: 'struct max8997_platform_data' has no member named 'irq_base'
> drivers/misc/max8997-muic.c: In function 'max8997_muic_remove':
> drivers/misc/max8997-muic.c:474:17: error: 'struct max8997_platform_data' has no member named 'irq_base'
> Caused by commit 98d8618af377 ("mfd: add irq domain support for max8997
> interrupts").
> I have reverted that commit for today.
I've just reverted it, Thomas please submit a fixed version along with
the regulator patch.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-04-17 13:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-17 4:27 linux-next: build failure after merge of the final tree (regulator tree related) Stephen Rothwell
2012-04-17 13:55 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-08-16 5:16 Stephen Rothwell
2012-08-16 6:39 ` Arnd Bergmann
2012-08-16 10:58 ` Mark Brown
2012-04-16 5:52 Stephen Rothwell
2012-02-03 5:15 Stephen Rothwell
2012-02-03 11:02 ` Mark Brown
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=20120417135516.GF6652@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lrg@ti.com \
--cc=sfr@canb.auug.org.au \
--cc=thomas.abraham@linaro.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.