* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2010-09-14 3:43 Stephen Rothwell
2010-09-14 5:05 ` Arun MURTHY
2010-09-16 7:15 ` Arun MURTHY
0 siblings, 2 replies; 21+ messages in thread
From: Stephen Rothwell @ 2010-09-14 3:43 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, Arun Murthy
[-- Attachment #1: Type: text/plain, Size: 2607 bytes --]
Hi Samuel,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/built-in.o: In function `__crc_pwm_free':
(*ABS*+0x24ba6d1e): multiple definition of `__crc_pwm_free'
drivers/mfd/built-in.o: In function `.pwm_free':
(.text+0x1ab3c): multiple definition of `.pwm_free'
drivers/misc/built-in.o:(.text+0x2620c): first defined here
drivers/mfd/built-in.o: In function `__crc_pwm_request':
(*ABS*+0xc1f4ec93): multiple definition of `__crc_pwm_request'
drivers/mfd/built-in.o: In function `__crc_pwm_enable':
(*ABS*+0x9d09808d): multiple definition of `__crc_pwm_enable'
drivers/mfd/built-in.o: In function `.pwm_enable':
(.text+0x1abc8): multiple definition of `.pwm_enable'
drivers/misc/built-in.o:(.text+0x26278): first defined here
drivers/mfd/built-in.o: In function `.pwm_request':
(.text+0x1a774): multiple definition of `.pwm_request'
drivers/misc/built-in.o:(.text+0x2604c): first defined here
drivers/mfd/built-in.o: In function `pwm_config':
(.opd+0x1ce0): multiple definition of `pwm_config'
drivers/misc/built-in.o:(.opd+0x3000): first defined here
drivers/mfd/built-in.o: In function `pwm_free':
(.opd+0x1d28): multiple definition of `pwm_free'
drivers/misc/built-in.o:(.opd+0x2fd0): first defined here
drivers/mfd/built-in.o: In function `pwm_request':
(.opd+0x1cf8): multiple definition of `pwm_request'
drivers/misc/built-in.o:(.opd+0x2f58): first defined here
drivers/mfd/built-in.o: In function `__crc_pwm_disable':
(*ABS*+0xb0493b18): multiple definition of `__crc_pwm_disable'
drivers/mfd/built-in.o: In function `.pwm_disable':
(.text+0x1aa24): multiple definition of `.pwm_disable'
drivers/misc/built-in.o:(.text+0x2613c): first defined here
drivers/mfd/built-in.o: In function `pwm_enable':
(.opd+0x1d40): multiple definition of `pwm_enable'
drivers/misc/built-in.o:(.opd+0x2fe8): first defined here
drivers/mfd/built-in.o: In function `.pwm_config':
(.text+0x1a648): multiple definition of `.pwm_config'
drivers/misc/built-in.o:(.text+0x26358): first defined here
drivers/mfd/built-in.o: In function `pwm_disable':
(.opd+0x1d10): multiple definition of `pwm_disable'
drivers/misc/built-in.o:(.opd+0x2fb8): first defined here
drivers/mfd/built-in.o: In function `__crc_pwm_config':
(*ABS*+0xc23f5b9): multiple definition of `__crc_pwm_config'
Caused by commit 03f582a93ecca6e9584b622570022abf08ed03ec ("misc: Add
ab8500 pwm driver"). 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 --]
^ permalink raw reply [flat|nested] 21+ messages in thread* RE: linux-next: build failure after merge of the final tree (mfd tree related)
2010-09-14 3:43 linux-next: build failure after merge of the final tree (mfd tree related) Stephen Rothwell
@ 2010-09-14 5:05 ` Arun MURTHY
2010-09-16 7:15 ` Arun MURTHY
1 sibling, 0 replies; 21+ messages in thread
From: Arun MURTHY @ 2010-09-14 5:05 UTC (permalink / raw)
To: Stephen Rothwell, Samuel Ortiz
Cc: linux-next, linux-kernel, Linus WALLEIJ, Mattias WALLIN,
Srinidhi KASAGAR
Hi Stephen/Samuel,
The following patch fixes the build issue.
Thanks and Regards,
Arun R Murthy
-------------
diff --git a/drivers/mfd/Kconfig b/drivers/mfd/Kconfig index fbfe14a..841ce47 100644
--- a/drivers/mfd/Kconfig
+++ b/drivers/mfd/Kconfig
@@ -475,7 +475,7 @@ config EZX_PCAP
config AB8500_CORE
bool "ST-Ericsson AB8500 Mixed Signal Power Management chip"
- depends on GENERIC_HARDIRQS && ABX500_CORE
+ depends on GENERIC_HARDIRQS && ABX500_CORE && ARCH_U8500
select MFD_CORE
help
Select this option to enable access to AB8500 power management
------------
> -----Original Message-----
> From: Stephen Rothwell [mailto:sfr@canb.auug.org.au]
> Sent: Tuesday, September 14, 2010 9:13 AM
> To: Samuel Ortiz
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Arun
> MURTHY
> Subject: linux-next: build failure after merge of the final tree (mfd
> tree related)
>
> Hi Samuel,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mfd/built-in.o: In function `__crc_pwm_free':
> (*ABS*+0x24ba6d1e): multiple definition of `__crc_pwm_free'
> drivers/mfd/built-in.o: In function `.pwm_free':
> (.text+0x1ab3c): multiple definition of `.pwm_free'
> drivers/misc/built-in.o:(.text+0x2620c): first defined here
> drivers/mfd/built-in.o: In function `__crc_pwm_request':
> (*ABS*+0xc1f4ec93): multiple definition of `__crc_pwm_request'
> drivers/mfd/built-in.o: In function `__crc_pwm_enable':
> (*ABS*+0x9d09808d): multiple definition of `__crc_pwm_enable'
> drivers/mfd/built-in.o: In function `.pwm_enable':
> (.text+0x1abc8): multiple definition of `.pwm_enable'
> drivers/misc/built-in.o:(.text+0x26278): first defined here
> drivers/mfd/built-in.o: In function `.pwm_request':
> (.text+0x1a774): multiple definition of `.pwm_request'
> drivers/misc/built-in.o:(.text+0x2604c): first defined here
> drivers/mfd/built-in.o: In function `pwm_config':
> (.opd+0x1ce0): multiple definition of `pwm_config'
> drivers/misc/built-in.o:(.opd+0x3000): first defined here
> drivers/mfd/built-in.o: In function `pwm_free':
> (.opd+0x1d28): multiple definition of `pwm_free'
> drivers/misc/built-in.o:(.opd+0x2fd0): first defined here
> drivers/mfd/built-in.o: In function `pwm_request':
> (.opd+0x1cf8): multiple definition of `pwm_request'
> drivers/misc/built-in.o:(.opd+0x2f58): first defined here
> drivers/mfd/built-in.o: In function `__crc_pwm_disable':
> (*ABS*+0xb0493b18): multiple definition of `__crc_pwm_disable'
> drivers/mfd/built-in.o: In function `.pwm_disable':
> (.text+0x1aa24): multiple definition of `.pwm_disable'
> drivers/misc/built-in.o:(.text+0x2613c): first defined here
> drivers/mfd/built-in.o: In function `pwm_enable':
> (.opd+0x1d40): multiple definition of `pwm_enable'
> drivers/misc/built-in.o:(.opd+0x2fe8): first defined here
> drivers/mfd/built-in.o: In function `.pwm_config':
> (.text+0x1a648): multiple definition of `.pwm_config'
> drivers/misc/built-in.o:(.text+0x26358): first defined here
> drivers/mfd/built-in.o: In function `pwm_disable':
> (.opd+0x1d10): multiple definition of `pwm_disable'
> drivers/misc/built-in.o:(.opd+0x2fb8): first defined here
> drivers/mfd/built-in.o: In function `__crc_pwm_config':
> (*ABS*+0xc23f5b9): multiple definition of `__crc_pwm_config'
>
> Caused by commit 03f582a93ecca6e9584b622570022abf08ed03ec ("misc: Add
> ab8500 pwm driver"). I have reverted that commit for today.
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
^ permalink raw reply [flat|nested] 21+ messages in thread* RE: linux-next: build failure after merge of the final tree (mfd tree related)
2010-09-14 3:43 linux-next: build failure after merge of the final tree (mfd tree related) Stephen Rothwell
2010-09-14 5:05 ` Arun MURTHY
@ 2010-09-16 7:15 ` Arun MURTHY
2010-09-16 7:23 ` Stephen Rothwell
1 sibling, 1 reply; 21+ messages in thread
From: Arun MURTHY @ 2010-09-16 7:15 UTC (permalink / raw)
To: Stephen Rothwell, Samuel Ortiz
Cc: linux-next, linux-kernel, Linus WALLEIJ, Mattias WALLIN,
Srinidhi KASAGAR, Arun MURTHY
Hi Stephen,
> > Hi Samuel,
> >
> > After merging the final tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> >
> > drivers/mfd/built-in.o: In function `__crc_pwm_free':
> > (*ABS*+0x24ba6d1e): multiple definition of `__crc_pwm_free'
> > drivers/mfd/built-in.o: In function `.pwm_free':
> > (.text+0x1ab3c): multiple definition of `.pwm_free'
> > drivers/misc/built-in.o:(.text+0x2620c): first defined here
> > drivers/mfd/built-in.o: In function `__crc_pwm_request':
> > (*ABS*+0xc1f4ec93): multiple definition of `__crc_pwm_request'
> > drivers/mfd/built-in.o: In function `__crc_pwm_enable':
> > (*ABS*+0x9d09808d): multiple definition of `__crc_pwm_enable'
> > drivers/mfd/built-in.o: In function `.pwm_enable':
> > (.text+0x1abc8): multiple definition of `.pwm_enable'
> > drivers/misc/built-in.o:(.text+0x26278): first defined here
> > drivers/mfd/built-in.o: In function `.pwm_request':
> > (.text+0x1a774): multiple definition of `.pwm_request'
> > drivers/misc/built-in.o:(.text+0x2604c): first defined here
> > drivers/mfd/built-in.o: In function `pwm_config':
> > (.opd+0x1ce0): multiple definition of `pwm_config'
> > drivers/misc/built-in.o:(.opd+0x3000): first defined here
> > drivers/mfd/built-in.o: In function `pwm_free':
> > (.opd+0x1d28): multiple definition of `pwm_free'
> > drivers/misc/built-in.o:(.opd+0x2fd0): first defined here
> > drivers/mfd/built-in.o: In function `pwm_request':
> > (.opd+0x1cf8): multiple definition of `pwm_request'
> > drivers/misc/built-in.o:(.opd+0x2f58): first defined here
> > drivers/mfd/built-in.o: In function `__crc_pwm_disable':
> > (*ABS*+0xb0493b18): multiple definition of `__crc_pwm_disable'
> > drivers/mfd/built-in.o: In function `.pwm_disable':
> > (.text+0x1aa24): multiple definition of `.pwm_disable'
> > drivers/misc/built-in.o:(.text+0x2613c): first defined here
> > drivers/mfd/built-in.o: In function `pwm_enable':
> > (.opd+0x1d40): multiple definition of `pwm_enable'
> > drivers/misc/built-in.o:(.opd+0x2fe8): first defined here
> > drivers/mfd/built-in.o: In function `.pwm_config':
> > (.text+0x1a648): multiple definition of `.pwm_config'
> > drivers/misc/built-in.o:(.text+0x26358): first defined here
> > drivers/mfd/built-in.o: In function `pwm_disable':
> > (.opd+0x1d10): multiple definition of `pwm_disable'
> > drivers/misc/built-in.o:(.opd+0x2fb8): first defined here
> > drivers/mfd/built-in.o: In function `__crc_pwm_config':
> > (*ABS*+0xc23f5b9): multiple definition of `__crc_pwm_config'
> >
> > Caused by commit 03f582a93ecca6e9584b622570022abf08ed03ec ("misc: Add
> > ab8500 pwm driver"). I have reverted that commit for today.
> >
Please find the patch that fixes this build issue @
http://git.kernel.org/?p=linux/kernel/git/sameo/mfd-2.6.git;a=commit;h=f33bd494862cdc519db1f5d9b3f8214a1dd4c1ff
Kindly merge this patch.
Thanks and Regards,
Arun R Murthy
------------
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2010-09-16 7:15 ` Arun MURTHY
@ 2010-09-16 7:23 ` Stephen Rothwell
2010-09-16 8:51 ` Stephen Rothwell
0 siblings, 1 reply; 21+ messages in thread
From: Stephen Rothwell @ 2010-09-16 7:23 UTC (permalink / raw)
To: Arun MURTHY
Cc: Samuel Ortiz, linux-next, linux-kernel, Linus WALLEIJ,
Mattias WALLIN, Srinidhi KASAGAR
[-- Attachment #1: Type: text/plain, Size: 3267 bytes --]
Hi Arun,
On Thu, 16 Sep 2010 09:15:22 +0200 Arun MURTHY <arun.murthy@stericsson.com> wrote:
>
> > > After merging the final tree, today's linux-next build (powerpc
> > > allyesconfig) failed like this:
> > >
> > > drivers/mfd/built-in.o: In function `__crc_pwm_free':
> > > (*ABS*+0x24ba6d1e): multiple definition of `__crc_pwm_free'
> > > drivers/mfd/built-in.o: In function `.pwm_free':
> > > (.text+0x1ab3c): multiple definition of `.pwm_free'
> > > drivers/misc/built-in.o:(.text+0x2620c): first defined here
> > > drivers/mfd/built-in.o: In function `__crc_pwm_request':
> > > (*ABS*+0xc1f4ec93): multiple definition of `__crc_pwm_request'
> > > drivers/mfd/built-in.o: In function `__crc_pwm_enable':
> > > (*ABS*+0x9d09808d): multiple definition of `__crc_pwm_enable'
> > > drivers/mfd/built-in.o: In function `.pwm_enable':
> > > (.text+0x1abc8): multiple definition of `.pwm_enable'
> > > drivers/misc/built-in.o:(.text+0x26278): first defined here
> > > drivers/mfd/built-in.o: In function `.pwm_request':
> > > (.text+0x1a774): multiple definition of `.pwm_request'
> > > drivers/misc/built-in.o:(.text+0x2604c): first defined here
> > > drivers/mfd/built-in.o: In function `pwm_config':
> > > (.opd+0x1ce0): multiple definition of `pwm_config'
> > > drivers/misc/built-in.o:(.opd+0x3000): first defined here
> > > drivers/mfd/built-in.o: In function `pwm_free':
> > > (.opd+0x1d28): multiple definition of `pwm_free'
> > > drivers/misc/built-in.o:(.opd+0x2fd0): first defined here
> > > drivers/mfd/built-in.o: In function `pwm_request':
> > > (.opd+0x1cf8): multiple definition of `pwm_request'
> > > drivers/misc/built-in.o:(.opd+0x2f58): first defined here
> > > drivers/mfd/built-in.o: In function `__crc_pwm_disable':
> > > (*ABS*+0xb0493b18): multiple definition of `__crc_pwm_disable'
> > > drivers/mfd/built-in.o: In function `.pwm_disable':
> > > (.text+0x1aa24): multiple definition of `.pwm_disable'
> > > drivers/misc/built-in.o:(.text+0x2613c): first defined here
> > > drivers/mfd/built-in.o: In function `pwm_enable':
> > > (.opd+0x1d40): multiple definition of `pwm_enable'
> > > drivers/misc/built-in.o:(.opd+0x2fe8): first defined here
> > > drivers/mfd/built-in.o: In function `.pwm_config':
> > > (.text+0x1a648): multiple definition of `.pwm_config'
> > > drivers/misc/built-in.o:(.text+0x26358): first defined here
> > > drivers/mfd/built-in.o: In function `pwm_disable':
> > > (.opd+0x1d10): multiple definition of `pwm_disable'
> > > drivers/misc/built-in.o:(.opd+0x2fb8): first defined here
> > > drivers/mfd/built-in.o: In function `__crc_pwm_config':
> > > (*ABS*+0xc23f5b9): multiple definition of `__crc_pwm_config'
> > >
> > > Caused by commit 03f582a93ecca6e9584b622570022abf08ed03ec ("misc: Add
> > > ab8500 pwm driver"). I have reverted that commit for today.
> > >
> Please find the patch that fixes this build issue @
> http://git.kernel.org/?p=linux/kernel/git/sameo/mfd-2.6.git;a=commit;h=f33bd494862cdc519db1f5d9b3f8214a1dd4c1ff
That patch was in the tree that produced the error above. The patch you
quote is a fix for a different build problem.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2010-09-16 7:23 ` Stephen Rothwell
@ 2010-09-16 8:51 ` Stephen Rothwell
0 siblings, 0 replies; 21+ messages in thread
From: Stephen Rothwell @ 2010-09-16 8:51 UTC (permalink / raw)
To: Arun MURTHY
Cc: Samuel Ortiz, linux-next, linux-kernel, Linus WALLEIJ,
Mattias WALLIN, Srinidhi KASAGAR
[-- Attachment #1: Type: text/plain, Size: 571 bytes --]
Hi Arun,
On Thu, 16 Sep 2010 17:23:22 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > Please find the patch that fixes this build issue @
> > http://git.kernel.org/?p=linux/kernel/git/sameo/mfd-2.6.git;a=commit;h=f33bd494862cdc519db1f5d9b3f8214a1dd4c1ff
>
> That patch was in the tree that produced the error above. The patch you
> quote is a fix for a different build problem.
Oops, wrong error. I need to read better. Ignore this.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread
* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2010-12-20 8:21 Stephen Rothwell
2010-12-20 10:33 ` Samuel Ortiz
0 siblings, 1 reply; 21+ messages in thread
From: Stephen Rothwell @ 2010-12-20 8:21 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, Mark Brown
[-- Attachment #1: Type: text/plain, Size: 2766 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/built-in.o: In function `__crc_pwm_free':
(*ABS*+0x24ba6d1e): multiple definition of `__crc_pwm_free'
drivers/mfd/built-in.o: In function `.pwm_free':
(.text+0x1a2bc): multiple definition of `.pwm_free'
drivers/misc/built-in.o:(.text+0x32e40): first defined here
drivers/mfd/built-in.o: In function `__crc_pwm_request':
(*ABS*+0xc1f4ec93): multiple definition of `__crc_pwm_request'
drivers/mfd/built-in.o: In function `__crc_pwm_enable':
(*ABS*+0x9d09808d): multiple definition of `__crc_pwm_enable'
drivers/mfd/built-in.o: In function `.pwm_enable':
(.text+0x1a348): multiple definition of `.pwm_enable'
drivers/misc/built-in.o:(.text+0x32eac): first defined here
drivers/mfd/built-in.o: In function `.pwm_request':
(.text+0x19ff4): multiple definition of `.pwm_request'
drivers/misc/built-in.o:(.text+0x32c80): first defined here
drivers/mfd/built-in.o: In function `pwm_config':
(.opd+0x1e48): multiple definition of `pwm_config'
drivers/misc/built-in.o:(.opd+0x4158): first defined here
drivers/mfd/built-in.o: In function `pwm_free':
(.opd+0x1e90): multiple definition of `pwm_free'
drivers/misc/built-in.o:(.opd+0x4128): first defined here
drivers/mfd/built-in.o: In function `pwm_request':
(.opd+0x1e60): multiple definition of `pwm_request'
drivers/misc/built-in.o:(.opd+0x40b0): first defined here
drivers/mfd/built-in.o: In function `__crc_pwm_disable':
(*ABS*+0xb0493b18): multiple definition of `__crc_pwm_disable'
drivers/mfd/built-in.o: In function `.pwm_disable':
(.text+0x1a1a4): multiple definition of `.pwm_disable'
drivers/misc/built-in.o:(.text+0x32d70): first defined here
drivers/mfd/built-in.o: In function `pwm_enable':
(.opd+0x1ea8): multiple definition of `pwm_enable'
drivers/misc/built-in.o:(.opd+0x4140): first defined here
drivers/mfd/built-in.o: In function `.pwm_config':
(.text+0x19ec8): multiple definition of `.pwm_config'
drivers/misc/built-in.o:(.text+0x32f8c): first defined here
drivers/mfd/built-in.o: In function `pwm_disable':
(.opd+0x1e78): multiple definition of `pwm_disable'
drivers/misc/built-in.o:(.opd+0x4110): first defined here
drivers/mfd/built-in.o: In function `__crc_pwm_config':
(*ABS*+0xc23f5b9): multiple definition of `__crc_pwm_config'
Probably caused by commit 665ba7cafa19e2e2596ace30edc75ebec882e82d ("mfd:
Remove ARCH_U8500 dependency from AB8500") which allowed this driver to
be built in on PowerPC ...
Some of the above symbols are global in more than one place in our code ...
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 --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2010-12-20 8:21 Stephen Rothwell
@ 2010-12-20 10:33 ` Samuel Ortiz
2010-12-20 10:52 ` Mark Brown
0 siblings, 1 reply; 21+ messages in thread
From: Samuel Ortiz @ 2010-12-20 10:33 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Mark Brown
Hi Stephen,
On Mon, Dec 20, 2010 at 07:21:21PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
Ok, I removed Mark's commit, the MFD tree should build fine now.
I'm keeping this one for whenever we'll have a proper pwm framework.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2010-12-20 10:33 ` Samuel Ortiz
@ 2010-12-20 10:52 ` Mark Brown
2010-12-20 12:18 ` Mark Brown
0 siblings, 1 reply; 21+ messages in thread
From: Mark Brown @ 2010-12-20 10:52 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: Stephen Rothwell, linux-next, linux-kernel
On Mon, Dec 20, 2010 at 11:33:37AM +0100, Samuel Ortiz wrote:
> On Mon, Dec 20, 2010 at 07:21:21PM +1100, Stephen Rothwell wrote:
> > After merging the final tree, today's linux-next build (powerpc
> > allyesconfig) failed like this:
> Ok, I removed Mark's commit, the MFD tree should build fine now.
> I'm keeping this one for whenever we'll have a proper pwm framework.
It doesn't need dropping I think, the driver should just need a
dependency on HAVE_PWM adding.
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2010-12-20 10:52 ` Mark Brown
@ 2010-12-20 12:18 ` Mark Brown
0 siblings, 0 replies; 21+ messages in thread
From: Mark Brown @ 2010-12-20 12:18 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: Stephen Rothwell, linux-next, linux-kernel
On Mon, Dec 20, 2010 at 10:52:03AM +0000, Mark Brown wrote:
> On Mon, Dec 20, 2010 at 11:33:37AM +0100, Samuel Ortiz wrote:
> > Ok, I removed Mark's commit, the MFD tree should build fine now.
> > I'm keeping this one for whenever we'll have a proper pwm framework.
> It doesn't need dropping I think, the driver should just need a
> dependency on HAVE_PWM adding.
Meh, sorry, wrong way round.
^ permalink raw reply [flat|nested] 21+ messages in thread
* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2011-03-21 2:59 Stephen Rothwell
0 siblings, 0 replies; 21+ messages in thread
From: Stephen Rothwell @ 2011-03-21 2:59 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, MyungJoo Ham, Kyungmin Park
[-- 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 --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
@ 2011-03-21 8:12 함명주
0 siblings, 0 replies; 21+ messages in thread
From: 함명주 @ 2011-03-21 8:12 UTC (permalink / raw)
To: Stephen Rothwell, Samuel Ortiz
Cc: linux-next, linux-kernel, 박경민
> 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
^ permalink raw reply [flat|nested] 21+ messages in thread* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2011-03-28 3:52 Stephen Rothwell
0 siblings, 0 replies; 21+ messages in thread
From: Stephen Rothwell @ 2011-03-28 3:52 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, Andres Salomon
[-- Attachment #1: Type: text/plain, Size: 548 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/cs5535-mfd.c:30:22: error: asm/olpc.h: No such file or directory
Caused by commit fa1df691688f ("mfd: Add mfd_clone_cell(), convert
cs5535-mfd/olpc-xo1 to it").
I have reverted that commit (and commit adfa4bd4a8bf "mfd: OLPC: Clean up
names to match what OLPC actually uses" that conflicted with the revert).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2011-12-21 6:33 Stephen Rothwell
2011-12-21 10:51 ` Cousson, Benoit
2011-12-22 17:30 ` Samuel Ortiz
0 siblings, 2 replies; 21+ messages in thread
From: Stephen Rothwell @ 2011-12-21 6:33 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, Benoit Cousson
[-- Attachment #1: Type: text/plain, Size: 1150 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/twl-core.c: In function 'twl_probe':
drivers/mfd/twl-core.c:1212:22: error: 'TWL6030_IRQ_BASE' undeclared (first use in this function)
drivers/mfd/twl-core.c:1212:22: note: each undeclared identifier is reported only once for each function it appears in
drivers/mfd/twl-core.c:1213:39: error: 'TWL6030_BASE_NR_IRQS' undeclared (first use in this function)
drivers/mfd/twl-core.c:1215:22: error: 'TWL4030_IRQ_BASE' undeclared (first use in this function)
drivers/mfd/twl-core.c:1216:39: error: 'TWL4030_BASE_NR_IRQS' undeclared (first use in this function)
drivers/mfd/twl-core.c:1218:3: error: implicit declaration of function 'irq_domain_add_simple' [-Werror=implicit-function-declaration]
Caused by commit 4eea8b1d717d ("mfd: Add initial DT support for
twl4030/twl6030"). A missing include? Or a CONFIG problem?
This build does not have CONFIG_IRQ_DOMAIN 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: 836 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
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
1 sibling, 1 reply; 21+ messages in thread
From: Cousson, Benoit @ 2011-12-21 10:51 UTC (permalink / raw)
To: Stephen Rothwell, Samuel Ortiz; +Cc: linux-next, linux-kernel
Hi Stephen,
On 12/21/2011 7:33 AM, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mfd/twl-core.c: In function 'twl_probe':
> drivers/mfd/twl-core.c:1212:22: error: 'TWL6030_IRQ_BASE' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1212:22: note: each undeclared identifier is reported only once for each function it appears in
> drivers/mfd/twl-core.c:1213:39: error: 'TWL6030_BASE_NR_IRQS' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1215:22: error: 'TWL4030_IRQ_BASE' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1216:39: error: 'TWL4030_BASE_NR_IRQS' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1218:3: error: implicit declaration of function 'irq_domain_add_simple' [-Werror=implicit-function-declaration]
>
> Caused by commit 4eea8b1d717d ("mfd: Add initial DT support for
> twl4030/twl6030"). A missing include? Or a CONFIG problem?
Both in fact...
There are some nasty dependencies with that TWL driver and the IRQ
defined in OMAP headers only. I was fooled by the name of these macros.
I naively thought this could be fixed later as written in the comment I
added. I appears this is not the case :-(.
> This build does not have CONFIG_IRQ_DOMAIN set.
Ooops, I was not aware of that domain CONFIG. That one is an easy fix.
Samuel,
Just let me know if you will have time for an updated version before Xmas.
I'll try to fix that by using irq_alloc_descs to avoid these hard-coded
macros. It might conflict with the still hard coded GPIO IRQs range, but
I'll see if it work for DT only at least.
Thanks,
Benoit
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2011-12-21 10:51 ` Cousson, Benoit
@ 2011-12-21 12:24 ` Samuel Ortiz
0 siblings, 0 replies; 21+ messages in thread
From: Samuel Ortiz @ 2011-12-21 12:24 UTC (permalink / raw)
To: Cousson, Benoit; +Cc: Stephen Rothwell, linux-next, linux-kernel
Hi Benoit,
On Wed, Dec 21, 2011 at 11:51:27AM +0100, Cousson, Benoit wrote:
> Hi Stephen,
>
> On 12/21/2011 7:33 AM, Stephen Rothwell wrote:
> >Hi all,
> >
> >After merging the final tree, today's linux-next build (powerpc
> >allyesconfig) failed like this:
> >
> >drivers/mfd/twl-core.c: In function 'twl_probe':
> >drivers/mfd/twl-core.c:1212:22: error: 'TWL6030_IRQ_BASE' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1212:22: note: each undeclared identifier is reported only once for each function it appears in
> >drivers/mfd/twl-core.c:1213:39: error: 'TWL6030_BASE_NR_IRQS' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1215:22: error: 'TWL4030_IRQ_BASE' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1216:39: error: 'TWL4030_BASE_NR_IRQS' undeclared (first use in this function)
> >drivers/mfd/twl-core.c:1218:3: error: implicit declaration of function 'irq_domain_add_simple' [-Werror=implicit-function-declaration]
> >
> >Caused by commit 4eea8b1d717d ("mfd: Add initial DT support for
> >twl4030/twl6030"). A missing include? Or a CONFIG problem?
>
> Both in fact...
>
> There are some nasty dependencies with that TWL driver and the IRQ
> defined in OMAP headers only. I was fooled by the name of these
> macros.
> I naively thought this could be fixed later as written in the
> comment I added. I appears this is not the case :-(.
>
> >This build does not have CONFIG_IRQ_DOMAIN set.
>
> Ooops, I was not aware of that domain CONFIG. That one is an easy fix.
>
>
> Samuel,
>
> Just let me know if you will have time for an updated version before Xmas.
I have time to merge an updated version, yes.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
^ permalink raw reply [flat|nested] 21+ messages in thread
* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2011-12-21 6:33 Stephen Rothwell
2011-12-21 10:51 ` Cousson, Benoit
@ 2011-12-22 17:30 ` Samuel Ortiz
1 sibling, 0 replies; 21+ messages in thread
From: Samuel Ortiz @ 2011-12-22 17:30 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Benoit Cousson
Hi Stephen,
On Wed, Dec 21, 2011 at 05:33:01PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mfd/twl-core.c: In function 'twl_probe':
> drivers/mfd/twl-core.c:1212:22: error: 'TWL6030_IRQ_BASE' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1212:22: note: each undeclared identifier is reported only once for each function it appears in
> drivers/mfd/twl-core.c:1213:39: error: 'TWL6030_BASE_NR_IRQS' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1215:22: error: 'TWL4030_IRQ_BASE' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1216:39: error: 'TWL4030_BASE_NR_IRQS' undeclared (first use in this function)
> drivers/mfd/twl-core.c:1218:3: error: implicit declaration of function 'irq_domain_add_simple' [-Werror=implicit-function-declaration]
>
> Caused by commit 4eea8b1d717d ("mfd: Add initial DT support for
> twl4030/twl6030"). A missing include? Or a CONFIG problem?
>
> This build does not have CONFIG_IRQ_DOMAIN set.
>
> I have reverted that commit for today.
I just pushed Benoit's new patch, this build failure should be fixed now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
^ permalink raw reply [flat|nested] 21+ messages in thread
* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2012-09-17 11:38 Stephen Rothwell
2012-09-17 13:28 ` Samuel Ortiz
0 siblings, 1 reply; 21+ messages in thread
From: Stephen Rothwell @ 2012-09-17 11:38 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, Gyungoh Yoo, Stephen Warren
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/max8907.c: In function 'max8907_i2c_probe':
drivers/mfd/max8907.c:248:10: error: too few arguments to function 'mfd_add_devices'
include/linux/mfd/core.h:100:12: note: declared here
Caused by commit 6c2591532a6f ("mfd: Add MAX8907 core driver") from the
mfd tree interacting with commit 0848c94fb4a5 ("mfd: core: Push irqdomain
mapping out into devices") from Linus' tree.
I have added the following patch and will carry it as a merge fix:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 17 Sep 2012 21:31:20 +1000
Subject: [PATCH] mfd: fix up for mfd_add_devices() API change
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
drivers/mfd/max8907.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/max8907.c b/drivers/mfd/max8907.c
index 5295276..6497c98 100644
--- a/drivers/mfd/max8907.c
+++ b/drivers/mfd/max8907.c
@@ -245,7 +245,7 @@ static __devinit int max8907_i2c_probe(struct i2c_client *i2c,
enable_irq(max8907->i2c_gen->irq);
ret = mfd_add_devices(max8907->dev, -1, max8907_cells,
- ARRAY_SIZE(max8907_cells), NULL, 0);
+ ARRAY_SIZE(max8907_cells), NULL, 0, NULL);
if (ret != 0) {
dev_err(&i2c->dev, "failed to add MFD devices %d\n", ret);
goto err_add_devices;
--
1.7.10.280.gaa39
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply related [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2012-09-17 11:38 Stephen Rothwell
@ 2012-09-17 13:28 ` Samuel Ortiz
0 siblings, 0 replies; 21+ messages in thread
From: Samuel Ortiz @ 2012-09-17 13:28 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Gyungoh Yoo, Stephen Warren
Hi Stephen,
On Mon, Sep 17, 2012 at 09:38:33PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mfd/max8907.c: In function 'max8907_i2c_probe':
> drivers/mfd/max8907.c:248:10: error: too few arguments to function 'mfd_add_devices'
> include/linux/mfd/core.h:100:12: note: declared here
>
> Caused by commit 6c2591532a6f ("mfd: Add MAX8907 core driver") from the
> mfd tree interacting with commit 0848c94fb4a5 ("mfd: core: Push irqdomain
> mapping out into devices") from Linus' tree.
My bad. And Stephen even warned me about it...
It should be all fixed now, sorry about that.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
^ permalink raw reply [flat|nested] 21+ messages in thread
* linux-next: build failure after merge of the final tree (mfd tree related)
@ 2013-06-18 7:19 Stephen Rothwell
2013-06-19 8:24 ` Samuel Ortiz
0 siblings, 1 reply; 21+ messages in thread
From: Stephen Rothwell @ 2013-06-18 7:19 UTC (permalink / raw)
To: Samuel Ortiz; +Cc: linux-next, linux-kernel, Chao Xie, Yi Zhang
[-- Attachment #1: Type: text/plain, Size: 813 bytes --]
Hi all,
After merging the final tree, today's linux-next build (powerpc
allyesconfig) failed like this:
drivers/mfd/88pm800.c: In function 'pm800_pages_init':
drivers/mfd/88pm800.c:434:2: error: implicit declaration of function 'IS_ERR' [-Werror=implicit-function-declaration]
if (IS_ERR(subchip->regmap_power)) {
^
drivers/mfd/88pm800.c:435:3: error: implicit declaration of function 'PTR_ERR' [-Werror=implicit-function-declaration]
ret = PTR_ERR(subchip->regmap_power);
^
Caused by commit f8ca616f67f7 ("mfd: 88pm800: Enhance error handling for
sub pages probe/remove") from the mfd tree. Forgot to include
linux/err.h (see Rule 1 in Documentation/SubmitChecklist).
I have reverted that commit for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
^ permalink raw reply [flat|nested] 21+ messages in thread* Re: linux-next: build failure after merge of the final tree (mfd tree related)
2013-06-18 7:19 Stephen Rothwell
@ 2013-06-19 8:24 ` Samuel Ortiz
2013-06-20 2:25 ` Chao Xie
0 siblings, 1 reply; 21+ messages in thread
From: Samuel Ortiz @ 2013-06-19 8:24 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Chao Xie, Yi Zhang
Hi Stephen,
On Tue, Jun 18, 2013 at 05:19:57PM +1000, Stephen Rothwell wrote:
> Hi all,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mfd/88pm800.c: In function 'pm800_pages_init':
> drivers/mfd/88pm800.c:434:2: error: implicit declaration of function 'IS_ERR' [-Werror=implicit-function-declaration]
> if (IS_ERR(subchip->regmap_power)) {
> ^
> drivers/mfd/88pm800.c:435:3: error: implicit declaration of function 'PTR_ERR' [-Werror=implicit-function-declaration]
> ret = PTR_ERR(subchip->regmap_power);
> ^
>
> Caused by commit f8ca616f67f7 ("mfd: 88pm800: Enhance error handling for
> sub pages probe/remove") from the mfd tree. Forgot to include
> linux/err.h (see Rule 1 in Documentation/SubmitChecklist).
Sorry about that. This is fixed now.
Cheers,
Samuel.
--
Intel Open Source Technology Centre
http://oss.intel.com/
^ permalink raw reply [flat|nested] 21+ messages in thread* RE: linux-next: build failure after merge of the final tree (mfd tree related)
2013-06-19 8:24 ` Samuel Ortiz
@ 2013-06-20 2:25 ` Chao Xie
0 siblings, 0 replies; 21+ messages in thread
From: Chao Xie @ 2013-06-20 2:25 UTC (permalink / raw)
To: Samuel Ortiz, Stephen Rothwell; +Cc: linux-next, linux-kernel, Yi Zhang
> -----Original Message-----
> From: Samuel Ortiz [mailto:sameo@linux.intel.com]
> Sent: Wednesday, June 19, 2013 4:25 PM
> To: Stephen Rothwell
> Cc: linux-next@vger.kernel.org; linux-kernel@vger.kernel.org; Chao Xie; Yi Zhang
> Subject: Re: linux-next: build failure after merge of the final tree (mfd tree related)
> Hi Stephen,
>>On Tue, Jun 18, 2013 at 05:19:57PM +1000, Stephen Rothwell wrote:
>> Hi all,
>>
>> After merging the final tree, today's linux-next build (powerpc
>> allyesconfig) failed like this:
>>
>> drivers/mfd/88pm800.c: In function 'pm800_pages_init':
>> drivers/mfd/88pm800.c:434:2: error: implicit declaration of function 'IS_ERR' [-Werror=implicit-function-declaration]
>> if (IS_ERR(subchip->regmap_power)) {
>> ^
>> drivers/mfd/88pm800.c:435:3: error: implicit declaration of function 'PTR_ERR' [-Werror=implicit-function-declaration]
>> ret = PTR_ERR(subchip->regmap_power);
>> ^
>>
>> Caused by commit f8ca616f67f7 ("mfd: 88pm800: Enhance error handling for
>> sub pages probe/remove") from the mfd tree. Forgot to include
>> linux/err.h (see Rule 1 in Documentation/SubmitChecklist).
>Sorry about that. This is fixed now.
It is my fault. Thanks for fixing it.
> Cheers,
> Samuel.
> --
> Intel Open Source Technology Centre
> http://oss.intel.com/
^ permalink raw reply [flat|nested] 21+ messages in thread
end of thread, other threads:[~2013-06-20 2:25 UTC | newest]
Thread overview: 21+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-09-14 3:43 linux-next: build failure after merge of the final tree (mfd tree related) 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
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
2011-03-21 2:59 Stephen Rothwell
2011-03-21 8:12 함명주
2011-03-28 3:52 Stephen Rothwell
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
2012-09-17 11:38 Stephen Rothwell
2012-09-17 13:28 ` Samuel Ortiz
2013-06-18 7:19 Stephen Rothwell
2013-06-19 8:24 ` Samuel Ortiz
2013-06-20 2:25 ` Chao Xie
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).