RE: linux-next: Tree for July 17 (mfd/tps65217.c)
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: > >>> > 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' > >>> > >>> > >>> Full randconfig file is attached. > >>> CONFIG_REGULATOR is not enabled. > >>> > >> > >> > >> This build error is still present in linux-next of 20120803. > >> > > > > This will be fixed with this patch > > https://patchwork.kernel.org/patch/1220151/ > > > > Today, I will submit v2 for this > > > This build still fails in linux-next 20120821. Could you please push this patch ASAP? http://www.spinics.net/lists/linux-omap/msg75336.html Thanks AnilKumar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd/tps65217.c)
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: >>> >>> drivers/built-in.o: In function `tps65217_probe': >>> tps65217.c:(.devinit.text+0x13e37): undefined reference to >>> `of_regulator_match' >>> >>> >>> Full randconfig file is attached. >>> CONFIG_REGULATOR is not enabled. >>> >> >> >> This build error is still present in linux-next of 20120803. >> > > This will be fixed with this patch > https://patchwork.kernel.org/patch/1220151/ > > Today, I will submit v2 for this This build still fails in linux-next 20120821. -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: linux-next: Tree for July 17 (mfd/tps65217.c)
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: 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' Full randconfig file is attached. CONFIG_REGULATOR is not enabled. This build error is still present in linux-next of 20120803. This will be fixed with this patch https://patchwork.kernel.org/patch/1220151/ Today, I will submit v2 for this This build still fails in linux-next 20120821. Could you please push this patch ASAP? http://www.spinics.net/lists/linux-omap/msg75336.html Thanks AnilKumar -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd/tps65217.c)
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: drivers/built-in.o: In function `tps65217_probe': tps65217.c:(.devinit.text+0x13e37): undefined reference to `of_regulator_match' Full randconfig file is attached. CONFIG_REGULATOR is not enabled. This build error is still present in linux-next of 20120803. This will be fixed with this patch https://patchwork.kernel.org/patch/1220151/ Today, I will submit v2 for this This build still fails in linux-next 20120821. -- ~Randy -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: linux-next: Tree for July 17 (mfd/tps65217.c)
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': > > tps65217.c:(.devinit.text+0x13e37): undefined reference to > > `of_regulator_match' > > > > > > Full randconfig file is attached. > > CONFIG_REGULATOR is not enabled. > > > > > This build error is still present in linux-next of 20120803. > This will be fixed with this patch https://patchwork.kernel.org/patch/1220151/ Today, I will submit v2 for this Regards AnilKumar -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
RE: linux-next: Tree for July 17 (mfd/tps65217.c)
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': tps65217.c:(.devinit.text+0x13e37): undefined reference to `of_regulator_match' Full randconfig file is attached. CONFIG_REGULATOR is not enabled. This build error is still present in linux-next of 20120803. This will be fixed with this patch https://patchwork.kernel.org/patch/1220151/ Today, I will submit v2 for this Regards AnilKumar -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd/tps65217.c)
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' > > > Full randconfig file is attached. > CONFIG_REGULATOR is not enabled. > This build error is still present in linux-next of 20120803. -- ~Randy -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd/tps65217.c)
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' Full randconfig file is attached. CONFIG_REGULATOR is not enabled. This build error is still present in linux-next of 20120803. -- ~Randy -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
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: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
On Wed, Jul 18, 2012 at 7:54 PM, Sedat Dilek sedat.di...@gmail.com 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: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)
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. >> >> I see the following call-trace in linux-next (next-20120717). >> >> [ 23.431889] [ cut here ] >> [ 23.431896] WARNING: at lib/debugobjects.c:261 >> debug_print_object+0x8e/0xb0() >> [ 23.431897] Hardware name: >> [ 23.431901] ODEBUG: free active (active state 0) object type: >> timer_list hint: delayed_work_timer_fn+0x0/0x40 > There are few delayed works on hci_dev structure, it's hard to say which > one is not stopped before kfree. > >> # CONFIG_DEBUG_OBJECTS_WORK is not set > If you enable that option, it should show which delayed work is causing > trouble. > OK, thanks for the explanations & hints! I will activate that kconfig-option. FYI: With yesterday's linux-next (next-20120719) I didn't trap into this regression (same kernel-config + several bootups). - Sedat - > Stanislaw -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)
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). > > [ 23.431889] [ cut here ] > [ 23.431896] WARNING: at lib/debugobjects.c:261 > debug_print_object+0x8e/0xb0() > [ 23.431897] Hardware name: > [ 23.431901] ODEBUG: free active (active state 0) object type: > timer_list hint: delayed_work_timer_fn+0x0/0x40 There are few delayed works on hci_dev structure, it's hard to say which one is not stopped before kfree. > # CONFIG_DEBUG_OBJECTS_WORK is not set If you enable that option, it should show which delayed work is causing trouble. Stanislaw -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)
On Wed, Jul 18, 2012 at 08:06:17PM +0200, Sedat Dilek wrote: On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell s...@canb.auug.org.au 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). [ 23.431889] [ cut here ] [ 23.431896] WARNING: at lib/debugobjects.c:261 debug_print_object+0x8e/0xb0() [ 23.431897] Hardware name: HIDDEN [ 23.431901] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x40 There are few delayed works on hci_dev structure, it's hard to say which one is not stopped before kfree. # CONFIG_DEBUG_OBJECTS_WORK is not set If you enable that option, it should show which delayed work is causing trouble. Stanislaw -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (debugobjects: bt | btusb | usb related?)
On Fri, Jul 20, 2012 at 11:47 AM, Stanislaw Gruszka sgrus...@redhat.com 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 s...@canb.auug.org.au 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). [ 23.431889] [ cut here ] [ 23.431896] WARNING: at lib/debugobjects.c:261 debug_print_object+0x8e/0xb0() [ 23.431897] Hardware name: HIDDEN [ 23.431901] ODEBUG: free active (active state 0) object type: timer_list hint: delayed_work_timer_fn+0x0/0x40 There are few delayed works on hci_dev structure, it's hard to say which one is not stopped before kfree. # CONFIG_DEBUG_OBJECTS_WORK is not set If you enable that option, it should show which delayed work is causing trouble. OK, thanks for the explanations hints! I will activate that kconfig-option. FYI: With yesterday's linux-next (next-20120719) I didn't trap into this regression (same kernel-config + several bootups). - Sedat - Stanislaw -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
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: rand_initialize_irq(client->irq); >>> >>> ...but why has random.h still this...? >>> >>> include/linux/random.h:51:extern void rand_initialize_irq(int irq); >>> >>> Just thinking "loud"... >>> >>> - Sedat - >> >> Is this attached patch OK, Ted? > > You're just deleting a line from the AB3100 driver, so I guess you're > regressing the system since that IRQ will no longer contribute > to the entropy pool? > > How do we simultaneously make sure that this IRQ is still > contributing to the entropy? > For the sake of completeness: * Ted explained in his answer in [1]. * Just FYI: [2] has these changes merged into the original commit. - Sedat - [1] http://marc.info/?l=linux-next=134256445707799=2 [2] http://git.kernel.org/?p=linux/kernel/git/tytso/random.git;a=commitdiff;h=627574db8b21c51217c683909458500916e64963 > Yours, > Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17
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 pgpOPGrwS6re9.pgp Description: PGP signature
Re: linux-next: Tree for July 17
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 message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17
On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell s...@canb.auug.org.au 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 message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17
Hi Sedat, On Wed, 18 Jul 2012 11:27:01 +0200 Sedat Dilek sedat.di...@gmail.com 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 pgpOPGrwS6re9.pgp Description: PGP signature
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
On Tue, Jul 17, 2012 at 8:40 PM, Linus Walleij linus.wall...@linaro.org wrote: On Tue, Jul 17, 2012 at 12:39 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Tue, Jul 17, 2012 at 12:21 PM, Sedat Dilek sedat.di...@gmail.com 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 still this...? include/linux/random.h:51:extern void rand_initialize_irq(int irq); Just thinking loud... - Sedat - Is this attached patch OK, Ted? You're just deleting a line from the AB3100 driver, so I guess you're regressing the system since that IRQ will no longer contribute to the entropy pool? How do we simultaneously make sure that this IRQ is still contributing to the entropy? For the sake of completeness: * Ted explained in his answer in [1]. * Just FYI: [2] has these changes merged into the original commit. - Sedat - [1] http://marc.info/?l=linux-nextm=134256445707799w=2 [2] http://git.kernel.org/?p=linux/kernel/git/tytso/random.git;a=commitdiff;h=627574db8b21c51217c683909458500916e64963 Yours, Linus Walleij -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (fs/sync.c)
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 function 'iterate_bdevs'
>
>
> Full randconfig file is attached.
According to https://lkml.org/lkml/2012/7/17/61, it happens for
!CONFIG_BLOCK
Also in e.g. sh-allnoconfig,
http://kisskb.ellerman.id.au/kisskb/buildresult/6722464/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
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 still this...? >> >> include/linux/random.h:51:extern void rand_initialize_irq(int irq); >> >> Just thinking "loud"... >> >> - Sedat - > > Is this attached patch OK, Ted? You're just deleting a line from the AB3100 driver, so I guess you're regressing the system since that IRQ will no longer contribute to the entropy pool? How do we simultaneously make sure that this IRQ is still contributing to the entropy? Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
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 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 used the >>> version from next-20120712. >>> >>> I have still reverted 3 commits from the signal tree at the request of the >>> arm maintainer. >>> >>> The akpm tree lost a few patches that turned up elsewhere. >>> >> >> From my today's build-log on a Ubuntu/precise AMD64 host: >> [...] >> LD drivers/video/built-in.o >> LD drivers/built-in.o >> LINKvmlinux >> LD vmlinux.o >> MODPOST vmlinux.o >> GEN .version >> CHK include/generated/compile.h >> UPD include/generated/compile.h >> CC init/version.o >> LD init/built-in.o >> drivers/built-in.o: In function `ab3100_probe': >> ab3100-core.c:(.devinit.text+0xbf97): undefined reference to >> `rand_initialize_irq' >> make[2]: *** [vmlinux] Error 1 >> make[1]: *** [deb-pkg] Error 2 >> make: *** [deb-pkg] Error 2 >> >> MFD / AB3100 kernel-config settings: >> >> CONFIG_AB3100_CORE=y >> CONFIG_AB3100_OTP=m >> CONFIG_REGULATOR_AB3100=m >> CONFIG_RTC_DRV_AB3100=m >> >> If you need further informations, please let me know. >> >> - Sedat - > > [ CC Ted (new random maintainer) ] > > Is this due to this change? > > From 946672f548682905d8ecdab33bb6e2c705418505 Mon Sep 17 00:00:00 2001 > From: Theodore Ts'o > Date: Sat, 14 Jul 2012 20:27:52 -0400 > Subject: [PATCH] random: remove rand_initialize_irq() > > With the new interrupt sampling system, we are no longer using the > timer_rand_state structure in the irq descriptor, so we can stop > initializing it now. > > Signed-off-by: "Theodore Ts'o" > ...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 still this...? > > include/linux/random.h:51:extern void rand_initialize_irq(int irq); > > Just thinking "loud"... > > - Sedat - Is this attached patch OK, Ted? - Sedat - 0001-random-remove-remaining-relicts-of-rand_initialize_i.patch Description: Binary data
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
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 build failure. >> >> The regulator tree gained conflicts against the mfd tree. >> >> The tty tree lost its build failure but gained another, so I used the >> version from next-20120712. >> >> I have still reverted 3 commits from the signal tree at the request of the >> arm maintainer. >> >> The akpm tree lost a few patches that turned up elsewhere. >> > > From my today's build-log on a Ubuntu/precise AMD64 host: > [...] > LD drivers/video/built-in.o > LD drivers/built-in.o > LINKvmlinux > LD vmlinux.o > MODPOST vmlinux.o > GEN .version > CHK include/generated/compile.h > UPD include/generated/compile.h > CC init/version.o > LD init/built-in.o > drivers/built-in.o: In function `ab3100_probe': > ab3100-core.c:(.devinit.text+0xbf97): undefined reference to > `rand_initialize_irq' > make[2]: *** [vmlinux] Error 1 > make[1]: *** [deb-pkg] Error 2 > make: *** [deb-pkg] Error 2 > > MFD / AB3100 kernel-config settings: > > CONFIG_AB3100_CORE=y > CONFIG_AB3100_OTP=m > CONFIG_REGULATOR_AB3100=m > CONFIG_RTC_DRV_AB3100=m > > If you need further informations, please let me know. > > - Sedat - [ CC Ted (new random maintainer) ] Is this due to this change? >From 946672f548682905d8ecdab33bb6e2c705418505 Mon Sep 17 00:00:00 2001 From: Theodore Ts'o Date: Sat, 14 Jul 2012 20:27:52 -0400 Subject: [PATCH] random: remove rand_initialize_irq() With the new interrupt sampling system, we are no longer using the timer_rand_state structure in the irq descriptor, so we can stop initializing it now. Signed-off-by: "Theodore Ts'o" irq); ...but why has random.h still this...? include/linux/random.h:51:extern void rand_initialize_irq(int irq); Just thinking "loud"... - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
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 mfd tree. > > The tty tree lost its build failure but gained another, so I used the > version from next-20120712. > > I have still reverted 3 commits from the signal tree at the request of the > arm maintainer. > > The akpm tree lost a few patches that turned up elsewhere. > >From my today's build-log on a Ubuntu/precise AMD64 host: [...] LD drivers/video/built-in.o LD drivers/built-in.o LINKvmlinux LD vmlinux.o MODPOST vmlinux.o GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o LD init/built-in.o drivers/built-in.o: In function `ab3100_probe': ab3100-core.c:(.devinit.text+0xbf97): undefined reference to `rand_initialize_irq' make[2]: *** [vmlinux] Error 1 make[1]: *** [deb-pkg] Error 2 make: *** [deb-pkg] Error 2 MFD / AB3100 kernel-config settings: CONFIG_AB3100_CORE=y CONFIG_AB3100_OTP=m CONFIG_REGULATOR_AB3100=m CONFIG_RTC_DRV_AB3100=m If you need further informations, please let me know. - Sedat - -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell s...@canb.auug.org.au 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 mfd tree. The tty tree lost its build failure but gained another, so I used the version from next-20120712. I have still reverted 3 commits from the signal tree at the request of the arm maintainer. The akpm tree lost a few patches that turned up elsewhere. From my today's build-log on a Ubuntu/precise AMD64 host: [...] LD drivers/video/built-in.o LD drivers/built-in.o LINKvmlinux LD vmlinux.o MODPOST vmlinux.o GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o LD init/built-in.o drivers/built-in.o: In function `ab3100_probe': ab3100-core.c:(.devinit.text+0xbf97): undefined reference to `rand_initialize_irq' make[2]: *** [vmlinux] Error 1 make[1]: *** [deb-pkg] Error 2 make: *** [deb-pkg] Error 2 MFD / AB3100 kernel-config settings: CONFIG_AB3100_CORE=y CONFIG_AB3100_OTP=m CONFIG_REGULATOR_AB3100=m CONFIG_RTC_DRV_AB3100=m If you need further informations, please let me know. - Sedat - -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
On Tue, Jul 17, 2012 at 11:47 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell s...@canb.auug.org.au 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 mfd tree. The tty tree lost its build failure but gained another, so I used the version from next-20120712. I have still reverted 3 commits from the signal tree at the request of the arm maintainer. The akpm tree lost a few patches that turned up elsewhere. From my today's build-log on a Ubuntu/precise AMD64 host: [...] LD drivers/video/built-in.o LD drivers/built-in.o LINKvmlinux LD vmlinux.o MODPOST vmlinux.o GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o LD init/built-in.o drivers/built-in.o: In function `ab3100_probe': ab3100-core.c:(.devinit.text+0xbf97): undefined reference to `rand_initialize_irq' make[2]: *** [vmlinux] Error 1 make[1]: *** [deb-pkg] Error 2 make: *** [deb-pkg] Error 2 MFD / AB3100 kernel-config settings: CONFIG_AB3100_CORE=y CONFIG_AB3100_OTP=m CONFIG_REGULATOR_AB3100=m CONFIG_RTC_DRV_AB3100=m If you need further informations, please let me know. - Sedat - [ CC Ted (new random maintainer) ] Is this due to this change? From 946672f548682905d8ecdab33bb6e2c705418505 Mon Sep 17 00:00:00 2001 From: Theodore Ts'o ty...@mit.edu Date: Sat, 14 Jul 2012 20:27:52 -0400 Subject: [PATCH] random: remove rand_initialize_irq() With the new interrupt sampling system, we are no longer using the timer_rand_state structure in the irq descriptor, so we can stop initializing it now. Signed-off-by: Theodore Ts'o ty...@mit.edu ...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 still this...? include/linux/random.h:51:extern void rand_initialize_irq(int irq); Just thinking loud... - Sedat - -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
On Tue, Jul 17, 2012 at 12:21 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Tue, Jul 17, 2012 at 11:47 AM, Sedat Dilek sedat.di...@gmail.com wrote: On Tue, Jul 17, 2012 at 7:41 AM, Stephen Rothwell s...@canb.auug.org.au 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 mfd tree. The tty tree lost its build failure but gained another, so I used the version from next-20120712. I have still reverted 3 commits from the signal tree at the request of the arm maintainer. The akpm tree lost a few patches that turned up elsewhere. From my today's build-log on a Ubuntu/precise AMD64 host: [...] LD drivers/video/built-in.o LD drivers/built-in.o LINKvmlinux LD vmlinux.o MODPOST vmlinux.o GEN .version CHK include/generated/compile.h UPD include/generated/compile.h CC init/version.o LD init/built-in.o drivers/built-in.o: In function `ab3100_probe': ab3100-core.c:(.devinit.text+0xbf97): undefined reference to `rand_initialize_irq' make[2]: *** [vmlinux] Error 1 make[1]: *** [deb-pkg] Error 2 make: *** [deb-pkg] Error 2 MFD / AB3100 kernel-config settings: CONFIG_AB3100_CORE=y CONFIG_AB3100_OTP=m CONFIG_REGULATOR_AB3100=m CONFIG_RTC_DRV_AB3100=m If you need further informations, please let me know. - Sedat - [ CC Ted (new random maintainer) ] Is this due to this change? From 946672f548682905d8ecdab33bb6e2c705418505 Mon Sep 17 00:00:00 2001 From: Theodore Ts'o ty...@mit.edu Date: Sat, 14 Jul 2012 20:27:52 -0400 Subject: [PATCH] random: remove rand_initialize_irq() With the new interrupt sampling system, we are no longer using the timer_rand_state structure in the irq descriptor, so we can stop initializing it now. Signed-off-by: Theodore Ts'o ty...@mit.edu ...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 still this...? include/linux/random.h:51:extern void rand_initialize_irq(int irq); Just thinking loud... - Sedat - Is this attached patch OK, Ted? - Sedat - 0001-random-remove-remaining-relicts-of-rand_initialize_i.patch Description: Binary data
Re: linux-next: Tree for July 17 (mfd: AB3100 - ab3100_probe: undefined reference to `rand_initialize_irq')
On Tue, Jul 17, 2012 at 12:39 PM, Sedat Dilek sedat.di...@gmail.com wrote: On Tue, Jul 17, 2012 at 12:21 PM, Sedat Dilek sedat.di...@gmail.com 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 still this...? include/linux/random.h:51:extern void rand_initialize_irq(int irq); Just thinking loud... - Sedat - Is this attached patch OK, Ted? You're just deleting a line from the AB3100 driver, so I guess you're regressing the system since that IRQ will no longer contribute to the entropy pool? How do we simultaneously make sure that this IRQ is still contributing to the entropy? Yours, Linus Walleij -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: linux-next: Tree for July 17 (fs/sync.c)
On Tue, Jul 17, 2012 at 10:29 PM, Randy Dunlap rdun...@xenotime.net 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 function 'iterate_bdevs'
Full randconfig file is attached.
According to https://lkml.org/lkml/2012/7/17/61, it happens for
!CONFIG_BLOCK
Also in e.g. sh-allnoconfig,
http://kisskb.ellerman.id.au/kisskb/buildresult/6722464/
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say programmer or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
linux-next: Tree for July 17
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 used the version from next-20120712. I have still reverted 3 commits from the signal tree at the request of the arm maintainer. The akpm tree lost a few patches that turned up elsewhere. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use "git pull" to do so as that will try to merge the new linux-next release with the old one. You should use "git fetch" as mentioned in the FAQ on the wiki (see below). You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc, sparc64 and arm defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary. Below is a summary of the state of the merge. We are up to 197 trees (counting Linus' and 26 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do. Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. There is a wiki covering stuff to do with linux-next at http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (e5254a6 Merge branch 'gma500' (Alan's GMA patches)) Merging fixes/master (9023a40 Merge tag 'mmc-fixes-for-3.5-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc) Merging kbuild-current/rc-fixes (f8f5701 Linux 3.5-rc1) Merging arm-current/fixes (ff081e0 ARM: 7457/1: smp: Fix suspicious RCU originating from cpu_die()) Merging m68k-current/for-linus (d8ce726 m68k: Use generic strncpy_from_user(), strlen_user(), and strnlen_user()) Merging powerpc-merge/merge (50fb31c tty/hvc_opal: Fix debug function name) Merging sparc/master (d55de60 sparc64: remove unused function straddles_64bit_va_hole()) Merging net/master (310e158 net: respect GFP_DMA in __netdev_alloc_skb()) Merging sound-current/for-linus (68e67f4 ALSA: snd-usb: move calls to usb_set_interface) Merging pci-current/for-linus (314489b Merge tag 'fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc) Merging wireless/master (8a70e7f NFC: NCI module license 'unspecified' taints kernel) Merging driver-core.current/driver-core-linus (5becfb1 kmsg: merge continuation records while printing) Merging tty.current/tty-linus (84a1caf Linux 3.5-rc7) Merging usb.current/usb-linus (84a1caf Linux 3.5-rc7) Merging staging.current/staging-linus (6887a41 Linux 3.5-rc5) Merging char-misc.current/char-misc-linus (84a1caf Linux 3.5-rc7) Merging input-current/for-linus (e76b8ee Input: xpad - add Andamiro Pump It Up pad) Merging md-current/for-linus (2d4f4f3 md/raid1: fix use-after-free bug in RAID1 data-check code.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (c475c06 hwrng: atmel-rng - fix data valid check) Merging ide/master (39a50b4 Merge branch 'hfsplus') Merging dwmw2/master (244dc4e Merge git://git.infradead.org/users/dwmw2/random-2.6) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (15e06bf irqdomain: Fix debugfs formatting) Merging devicetree-current/devicetree/merge (4e8383b of: release node fix for of_parse_phandle_with_args) Merging spi-current/spi/merge (d1c185b of/spi: Fix SPI module loading by using proper "spi:" modalias prefixes.) Merging gpio-current/gpio/merge (96b7064 gpio/tca6424: merge I2C transactions, remove cast) Merging arm/for-next (dea2ea3 Merge branches 'audit', 'delay', 'dmaengine', 'fixes', 'misc' and 'sta2x11' into for-next) Merging arm-perf/for-next/perf (dee8c1b ARM: perf: remove arm_perf_pmu_ids global enumeration)
linux-next: Tree for July 17
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 used the version from next-20120712. I have still reverted 3 commits from the signal tree at the request of the arm maintainer. The akpm tree lost a few patches that turned up elsewhere. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at http://www.kernel.org/pub/linux/kernel/next/ ). If you are tracking the linux-next tree using git, you should not use git pull to do so as that will try to merge the new linux-next release with the old one. You should use git fetch as mentioned in the FAQ on the wiki (see below). You can see which trees have been included by looking in the Next/Trees file in the source. There are also quilt-import.log and merge.log files in the Next directory. Between each merge, the tree was built with a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the final fixups (if any), it is also built with powerpc allnoconfig (32 and 64 bit), ppc44x_defconfig and allyesconfig (minus CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc, sparc64 and arm defconfig. These builds also have CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and CONFIG_DEBUG_INFO disabled when necessary. Below is a summary of the state of the merge. We are up to 197 trees (counting Linus' and 26 trees of patches pending for Linus' tree), more are welcome (even if they are currently empty). Thanks to those who have contributed, and to those who haven't, please do. Status of my local build tests will be at http://kisskb.ellerman.id.au/linux-next . If maintainers want to give advice about cross compilers/configs that work, we are always open to add more builds. Thanks to Randy Dunlap for doing many randconfig builds. And to Paul Gortmaker for triage and bug fixes. There is a wiki covering stuff to do with linux-next at http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel. -- Cheers, Stephen Rothwells...@canb.auug.org.au $ git checkout master $ git reset --hard stable Merging origin/master (e5254a6 Merge branch 'gma500' (Alan's GMA patches)) Merging fixes/master (9023a40 Merge tag 'mmc-fixes-for-3.5-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc) Merging kbuild-current/rc-fixes (f8f5701 Linux 3.5-rc1) Merging arm-current/fixes (ff081e0 ARM: 7457/1: smp: Fix suspicious RCU originating from cpu_die()) Merging m68k-current/for-linus (d8ce726 m68k: Use generic strncpy_from_user(), strlen_user(), and strnlen_user()) Merging powerpc-merge/merge (50fb31c tty/hvc_opal: Fix debug function name) Merging sparc/master (d55de60 sparc64: remove unused function straddles_64bit_va_hole()) Merging net/master (310e158 net: respect GFP_DMA in __netdev_alloc_skb()) Merging sound-current/for-linus (68e67f4 ALSA: snd-usb: move calls to usb_set_interface) Merging pci-current/for-linus (314489b Merge tag 'fixes-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc) Merging wireless/master (8a70e7f NFC: NCI module license 'unspecified' taints kernel) Merging driver-core.current/driver-core-linus (5becfb1 kmsg: merge continuation records while printing) Merging tty.current/tty-linus (84a1caf Linux 3.5-rc7) Merging usb.current/usb-linus (84a1caf Linux 3.5-rc7) Merging staging.current/staging-linus (6887a41 Linux 3.5-rc5) Merging char-misc.current/char-misc-linus (84a1caf Linux 3.5-rc7) Merging input-current/for-linus (e76b8ee Input: xpad - add Andamiro Pump It Up pad) Merging md-current/for-linus (2d4f4f3 md/raid1: fix use-after-free bug in RAID1 data-check code.) Merging audit-current/for-linus (c158a35 audit: no leading space in audit_log_d_path prefix) Merging crypto-current/master (c475c06 hwrng: atmel-rng - fix data valid check) Merging ide/master (39a50b4 Merge branch 'hfsplus') Merging dwmw2/master (244dc4e Merge git://git.infradead.org/users/dwmw2/random-2.6) Merging sh-current/sh-fixes-for-linus (4403310 SH: Convert out[bwl] macros to inline functions) Merging irqdomain-current/irqdomain/merge (15e06bf irqdomain: Fix debugfs formatting) Merging devicetree-current/devicetree/merge (4e8383b of: release node fix for of_parse_phandle_with_args) Merging spi-current/spi/merge (d1c185b of/spi: Fix SPI module loading by using proper spi: modalias prefixes.) Merging gpio-current/gpio/merge (96b7064 gpio/tca6424: merge I2C transactions, remove cast) Merging arm/for-next (dea2ea3 Merge branches 'audit', 'delay', 'dmaengine', 'fixes', 'misc' and 'sta2x11' into for-next) Merging arm-perf/for-next/perf (dee8c1b ARM: perf: remove arm_perf_pmu_ids global enumeration)
