From: 함명주 <myungjoo.ham@samsung.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Samuel Ortiz <sameo@linux.intel.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
박경민 <kyungmin.park@samsung.com>
Subject: Re: linux-next: build failure after merge of the final tree (mfd tree related)
Date: Mon, 21 Mar 2011 08:12:53 +0000 (GMT) [thread overview]
Message-ID: <24090250.39821300695171946.JavaMail.weblogic@epml12> (raw)
> Sender : Stephen Rothwell<sfr@canb.auug.org.au>
> Date : 2011-03-21 11:59 (GMT+09:00)
> Title : linux-next: build failure after merge of the final tree (mfd tree related)
>
> 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.
Hello Stephen,
I've just submitted a corrected patch that works with
CONFIG_GENERIC_HARDIRQS_NO_DEPRECATED being either set or unset.
Because it appears that we still have targets with deprecated functions,
I left the deprecated functions working as well as the new ones.
Thank you.
- MyungJoo.
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
>
MyungJoo Ham (함명주)
Mobile Software Platform Lab,
Digital Media and Communications (DMC) Business
Samsung Electronics
cell: +82-10-6714-2858 / office: +82-31-279-8033
next reply other threads:[~2011-03-21 8:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 8:12 함명주 [this message]
-- 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 2:59 Stephen Rothwell
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=24090250.39821300695171946.JavaMail.weblogic@epml12 \
--to=myungjoo.ham@samsung.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sameo@linux.intel.com \
--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).