[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <25B60CDC2F704E4E9D88FFD52780CB4C04B6A37960@SC-VEXCH1.marvell.com>
Date: Mon, 5 Oct 2009 21:19:32 -0700
From: Haojian Zhuang <hzhuang1@...vell.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Samuel Ortiz <sameo@...nedhand.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Mark Brown <broonie@...nsource.wolfsonmicro.com>
Subject: RE: linux-next: mfd tree build failure
Hi Stephen,
Thanks a lot for your help. I fix it now. Please help to review it. It's already passed the build test.
Best Regards
Haojian
-----Original Message-----
From: Stephen Rothwell [mailto:sfr@...b.auug.org.au]
Sent: 2009年10月6日 11:54 AM
To: Haojian Zhuang
Cc: Samuel Ortiz; linux-next@...r.kernel.org; linux-kernel@...r.kernel.org; Mark Brown
Subject: Re: linux-next: mfd tree build failure
Hi Haojian,
On Mon, 5 Oct 2009 19:35:05 -0700 Haojian Zhuang <hzhuang1@...vell.com> wrote:
>
> Could you send your .config file to me? The 88pm8607 patch is just for mfd-2.6 git tree. I didn't try it in linux-next git tree before. I can try it now. If I could have your .config file, it would be better.
I am sorry, but I don't have the exact .config file any more (I have
moved on in my creation of linux-next) however, as I said, this was an
allmodconfig build on x86_64. I also noted that CONFIG_I2C=m and
CONFIG_MFD_CORE=m, while the config entry that controls the building of
this driver is a bool so must have been 'y'. So from a builtin driver,
you are referring to symbols that are only defined in modules.
--
Cheers,
Stephen Rothwell sfr@...b.auug.org.au
http://www.canb.auug.org.au/~sfr/
Download attachment "0002-mfd-fix-the-dependancy-issue-on-88PM8607.patch" of type "application/octet-stream" (959 bytes)
Powered by blists - more mailing lists