RE: linux-next: Tree for July 17 (mfd/tps65217.c)

2012-08-21 Thread AnilKumar, Chimata
Hi Samuel, On Tue, Aug 21, 2012 at 23:21:37, Randy Dunlap wrote: > On 08/05/2012 11:38 PM, AnilKumar, Chimata wrote: > > > On Fri, Aug 03, 2012 at 22:58:01, Randy Dunlap wrote: > >> On 07/17/2012 02:48 PM, Randy Dunlap wrote: > >> > >>> On 07/16/2012 10:41 PM, Stephen Rothwell wrote: > >>> >

Re: linux-next: Tree for July 17 (mfd/tps65217.c)

2012-08-21 Thread Randy Dunlap
On 08/05/2012 11:38 PM, AnilKumar, Chimata wrote: > On Fri, Aug 03, 2012 at 22:58:01, Randy Dunlap wrote: >> On 07/17/2012 02:48 PM, Randy Dunlap wrote: >> >>> On 07/16/2012 10:41 PM, Stephen Rothwell wrote: >>> Hi all, Changes since 20120716: >>> >>> >>> on i386: >>> >>> drive

RE: linux-next: Tree for July 17 (mfd/tps65217.c)

2012-08-05 Thread AnilKumar, Chimata
On Fri, Aug 03, 2012 at 22:58:01, Randy Dunlap wrote: > On 07/17/2012 02:48 PM, Randy Dunlap wrote: > > > On 07/16/2012 10:41 PM, Stephen Rothwell wrote: > > > >> Hi all, > >> > >> Changes since 20120716: > >> > > > > > > on i386: > > > > drivers/built-in.o: In function `tps65217_probe': > > t

Re: linux-next: Tree for July 17 (mfd/tps65217.c)

2012-08-03 Thread Randy Dunlap
On 07/17/2012 02:48 PM, Randy Dunlap wrote: > On 07/16/2012 10:41 PM, Stephen Rothwell wrote: > >> Hi all, >> >> Changes since 20120716: >> > > > on i386: > > drivers/built-in.o: In function `tps65217_probe': > tps65217.c:(.devinit.text+0x13e37): undefined reference to > `of_regulator_match'

Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')

2012-07-23 Thread Linus Walleij
On Wed, Jul 18, 2012 at 7:54 PM, Sedat Dilek wrote: > For the sake of completeness: > * Ted explained in his answer in [1]. > * Just FYI: [2] has these changes merged into the original commit. Yep I read up on it and I'm all fine with it. Thanks! Linus Walleij -- To unsubscribe from this list:

Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)

2012-07-20 Thread Sedat Dilek
On Fri, Jul 20, 2012 at 11:47 AM, Stanislaw Gruszka wrote: > On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote: >> On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell >> wrote: >> > Hi all, >> > >> > Changes since 20120716: >> > >> >> Not sure what the root cause of this issue is. >> >>

Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)

2012-07-20 Thread Stanislaw Gruszka
On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote: > On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell > wrote: > > Hi all, > > > > Changes since 20120716: > > > > Not sure what the root cause of this issue is. > > I see the following call-trace in linux-next (next-20120717). > > [

Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')

2012-07-18 Thread Sedat Dilek
On Tue, Jul 17, 2012 at 8:40 PM, Linus Walleij wrote: > On Tue, Jul 17, 2012 at 12:39 PM, Sedat Dilek wrote: >> On Tue, Jul 17, 2012 at 12:21 PM, Sedat Dilek wrote: >>> ...looks like AB3100 is the *only* driver still using >>> rand_initialize_irq()... >>> >>> drivers/mfd/ab3100-core.c:939: ran

Re: linux-next: Tree for July 17

2012-07-18 Thread Stephen Rothwell
Hi Sedat, On Wed, 18 Jul 2012 11:27:01 +0200 Sedat Dilek wrote: > > Out of curiosity (and normally you are giving a reason why there > is...) no new Tree for July 18? Yeah, I will send out a message. Thanks for prompting me. -- Cheers, Stephen Rothwells...@canb.auug.org.au

Re: linux-next: Tree for July 17

2012-07-18 Thread Sedat Dilek
On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20120716: > Out of curiosity (and normally you are giving a reason why there is...) no new Tree for July 18? - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a

Re: linux-next: Tree for July 17 (fs/sync.c)

2012-07-17 Thread Geert Uytterhoeven
On Tue, Jul 17, 2012 at 10:29 PM, Randy Dunlap wrote: > On 07/16/2012 10:41 PM, Stephen Rothwell wrote: > >> Hi all, >> >> Changes since 20120716: >> >> The vfs tree lost its build failure. > > > > on i386: > > fs/sync.c: In function 'sys_sync': > fs/sync.c:110:2: error: implicit declaration of fu

Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')

2012-07-17 Thread Linus Walleij
On Tue, Jul 17, 2012 at 12:39 PM, Sedat Dilek wrote: > On Tue, Jul 17, 2012 at 12:21 PM, Sedat Dilek wrote: >> ...looks like AB3100 is the *only* driver still using >> rand_initialize_irq()... >> >> drivers/mfd/ab3100-core.c:939: rand_initialize_irq(client->irq); >> >> ...but why has random.h s

Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')

2012-07-17 Thread Sedat Dilek
On Tue, Jul 17, 2012 at 12:21 PM, Sedat Dilek wrote: > On Tue, Jul 17, 2012 at 11:47 AM, Sedat Dilek wrote: >> On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell >> wrote: >>> Hi all, >>> >>> Changes since 20120716: >>> >>> The vfs tree lost its build failure. >>> >>> The l2-mtd tree gained a co

Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')

2012-07-17 Thread Sedat Dilek
On Tue, Jul 17, 2012 at 11:47 AM, Sedat Dilek wrote: > On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell > wrote: >> Hi all, >> >> Changes since 20120716: >> >> The vfs tree lost its build failure. >> >> The l2-mtd tree gained a conflict against the mtd tree. >> >> The battery tree tree lost its

Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')

2012-07-17 Thread Sedat Dilek
On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20120716: > > The vfs tree lost its build failure. > > The l2-mtd tree gained a conflict against the mtd tree. > > The battery tree tree lost its build failure. > > The regulator tree gained conflicts against the

linux-next: Tree for July 17

2012-07-16 Thread Stephen Rothwell
Hi all, Changes since 20120716: The vfs tree lost its build failure. The l2-mtd tree gained a conflict against the mtd tree. The battery tree tree lost its build failure. The regulator tree gained conflicts against the mfd tree. The tty tree lost its build failure but gained another, so I use