From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Samuel Ortiz <sameo@linux•intel.com>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
MyungJoo Ham <myungjoo.ham@samsung•com>,
Kyungmin Park <kyungmin.park@samsung•com>
Subject: linux-next: build failure after merge of the final tree (mfd tree related)
Date: Mon, 21 Mar 2011 13:59:10 +1100 [thread overview]
Message-ID: <20110321135910.267f367f.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1142 bytes --]
Hi Sam,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/max8997-irq.c:170: error: unknown field 'bus_lock' specified in initializer
drivers/mfd/max8997-irq.c:170: warning: initialization from incompatible pointer type
drivers/mfd/max8997-irq.c:171: error: unknown field 'bus_sync_unlock' specified in initializer
drivers/mfd/max8997-irq.c:171: warning: initialization from incompatible pointer type
drivers/mfd/max8997-irq.c:172: error: unknown field 'mask' specified in initializer
drivers/mfd/max8997-irq.c:172: warning: initialization from incompatible pointer type
drivers/mfd/max8997-irq.c:173: error: unknown field 'unmask' specified in initializer
drivers/mfd/max8997-irq.c:173: warning: initialization from incompatible pointer type
Caused by commit d7d21d394c9d ("mfd: Add MAX8997/8966 IRQ control feature").
The presence of these fields depends on
CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED not being set.
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next reply other threads:[~2011-03-21 2:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 2:59 Stephen Rothwell [this message]
2011-03-21 8:08 ` [PATCH v7] MAX8997/8966 MFD: Add IRQ control feature MyungJoo Ham
2011-03-22 11:51 ` Samuel Ortiz
2011-03-24 6:54 ` [PATCH] " MyungJoo Ham
-- strict thread matches above, loose matches on Subject: below --
2013-06-18 7:19 linux-next: build failure after merge of the final tree (mfd tree related) Stephen Rothwell
2013-06-19 8:24 ` Samuel Ortiz
2013-06-20 2:25 ` Chao Xie
2012-09-17 11:38 Stephen Rothwell
2012-09-17 13:28 ` Samuel Ortiz
2011-12-21 6:33 Stephen Rothwell
2011-12-21 10:51 ` Cousson, Benoit
2011-12-21 12:24 ` Samuel Ortiz
2011-12-22 17:30 ` Samuel Ortiz
2011-03-28 3:52 Stephen Rothwell
2011-03-21 8:12 함명주
2010-12-20 8:21 Stephen Rothwell
2010-12-20 10:33 ` Samuel Ortiz
2010-12-20 10:52 ` Mark Brown
2010-12-20 12:18 ` Mark Brown
2010-09-14 3:43 Stephen Rothwell
2010-09-14 5:05 ` Arun MURTHY
2010-09-16 7:15 ` Arun MURTHY
2010-09-16 7:23 ` Stephen Rothwell
2010-09-16 8:51 ` Stephen Rothwell
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=20110321135910.267f367f.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=kyungmin.park@samsung$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=myungjoo.ham@samsung$(echo .)com \
--cc=sameo@linux$(echo .)intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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