All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
	shuah.kh@samsung.com, patches@kernelci.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 3.14 00/23] 3.14.69-stable review
Date: Mon, 9 May 2016 06:20:53 -0700	[thread overview]
Message-ID: <57308EB5.30707@roeck-us.net> (raw)
In-Reply-To: <20160509071646.726412064@linuxfoundation.org>

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

  parent reply	other threads:[~2016-05-09 13:21 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09  7:17 [PATCH 3.14 00/23] 3.14.69-stable review Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 01/23] compiler-gcc: integrate the various compiler-gcc[345].h files Greg Kroah-Hartman
2016-05-11  9:27   ` Jiri Slaby
2016-05-14 23:41     ` Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 02/23] compiler-gcc: disable -ftracer for __noclone functions Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 04/23] ipvs: correct initial offset of Call-ID header search in SIP persistence engine Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 05/23] nbd: ratelimit error msgs after socket close Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 06/23] clk: versatile: sp810: support reentrance Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 07/23] lpfc: fix misleading indentation Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 08/23] tracing: Dont display trigger file for events that cant be enabled Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 09/23] ARM: SoCFPGA: Fix secondary CPU startup in thumb2 kernel Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 10/23] Input: zforce_ts - fix dual touch recognition Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 11/23] proc: prevent accessing /proc/<PID>/environ until its ready Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 12/23] batman-adv: Check skb size before using encapsulated ETH+VLAN header Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 14/23] batman-adv: Reduce refcnt of removed router when updating route Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 15/23] MAINTAINERS: Remove asterisk from EFI directory names Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 16/23] x86/tsc: Read all ratio bits from MSR_PLATFORM_INFO Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 17/23] x86/sysfb_efi: Fix valid BAR address range check Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 18/23] ACPICA: Dispatcher: Update thread ID for recursive method calls Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 19/23] USB: serial: cp210x: add ID for Link ECU Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 20/23] USB: serial: cp210x: add Straizona Focusers device ids Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 21/23] iio: ak8975: Fix NULL pointer exception on early interrupt Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 22/23] Input: ads7846 - correct the value got from SPI Greg Kroah-Hartman
2016-05-09  7:17 ` [PATCH 3.14 23/23] powerpc: scan_features() updates incorrect bits for REAL_LE Greg Kroah-Hartman
2016-05-09 13:20 ` Guenter Roeck [this message]
2016-05-09 18:21 ` [PATCH 3.14 00/23] 3.14.69-stable review Christoph Biedl
2016-05-10  7:03   ` Greg KH
2016-05-11  6:19     ` Christoph Biedl
2016-05-12 18:13   ` Christoph Biedl
2016-05-09 19:40 ` Shuah Khan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=57308EB5.30707@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patches@kernelci.org \
    --cc=shuah.kh@samsung.com \
    --cc=stable@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.