On 05/09/2016 12:17 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.69 release. There are 23 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Wed May 11 07:16:11 UTC 2016. Anything received after that time might be too late.
Build results: total: 129 pass: 129 fail: 0 Qemu test results: total: 90 pass: 90 fail: 0 Runtime warnings (mainstone:mainstone_defconfig): WARNING: CPU: 0 PID: 0 at kernel/irq/chip.c:670 __irq_set_handler+0x118/0x128() Modules linked in: CPU: 0 PID: 0 Comm: swapper Not tainted 3.14.68-00023-g982ed6e #1 [<c000d23c>] (unwind_backtrace) from [<c000b6ec>] (show_stack+0x10/0x14) [<c000b6ec>] (show_stack) from [<c0015628>] (warn_slowpath_common+0x6c/0x8c) [<c0015628>] (warn_slowpath_common) from [<c0015664>] (warn_slowpath_null+0x1c/0x24) [<c0015664>] (warn_slowpath_null) from [<c0042f58>] (__irq_set_handler+0x118/0x128) [<c0042f58>] (__irq_set_handler) from [<c0355a30>] (mainstone_init_irq+0x84/0xa4) [<c0355a30>] (mainstone_init_irq) from [<c0352154>] (init_IRQ+0x14/0x1c) [<c0352154>] (init_IRQ) from [<c03508d4>] (start_kernel+0x1b8/0x350) [<c03508d4>] (start_kernel) from [<a0008040>] (0xa0008040)70 __irq_set_handler+0x118/0x128() To be fair, this is not a new warning. Only reason for it to show up now is that I recently added mainstone to my list of tests. The problem is also seen with v3.14. I do not see it with the current mainline kernel, so it must have been fixed at some point. I may do a reverse bisect if I find the time. For the time being, this is not a concern. Details are available at http://kerneltests.org/builders. Guenter -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html