Re: [PATCH, RFC 14/22] oprofile: always enable IRQ_WORK

2013-05-03 Thread Arnd Bergmann
On Friday 03 May 2013, Steven Rostedt wrote: > On Fri, 2013-05-03 at 13:53 +0200, Robert Richter wrote: > > On 02.05.13 17:16:18, Arnd Bergmann wrote: > > > oprofile fails to build if CONFIG_IRQ_WORK is not already enabled, > > > because of the dependency on the RING_BUFFER code that now uses > > >

Re: [PATCH, RFC 14/22] oprofile: always enable IRQ_WORK

2013-05-03 Thread Steven Rostedt
On Fri, 2013-05-03 at 13:53 +0200, Robert Richter wrote: > On 02.05.13 17:16:18, Arnd Bergmann wrote: > > oprofile fails to build if CONFIG_IRQ_WORK is not already enabled, > > because of the dependency on the RING_BUFFER code that now uses > > the irq work library. > > > > kernel/built-in.o: In f

Re: [PATCH, RFC 14/22] oprofile: always enable IRQ_WORK

2013-05-03 Thread Steven Rostedt
On Fri, 2013-05-03 at 13:53 +0200, Robert Richter wrote: > On 02.05.13 17:16:18, Arnd Bergmann wrote: > > oprofile fails to build if CONFIG_IRQ_WORK is not already enabled, > > because of the dependency on the RING_BUFFER code that now uses > > the irq work library. > > > > kernel/built-in.o: In f

Re: [PATCH, RFC 14/22] oprofile: always enable IRQ_WORK

2013-05-03 Thread Robert Richter
On 02.05.13 17:16:18, Arnd Bergmann wrote: > oprofile fails to build if CONFIG_IRQ_WORK is not already enabled, > because of the dependency on the RING_BUFFER code that now uses > the irq work library. > > kernel/built-in.o: In function `ring_buffer_unlock_commit': > :(.text+0x5b8f0): undefined re