From: Guenter Roeck <linux@roeck-us.net>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org
Subject: (v4.4/v4.5)-stable-queue build and qemu failures (arm:allmodconfig, arm:pxa_defconfig, arm:omap2plus_defconfig)
Date: Fri, 29 Apr 2016 13:19:14 -0700 [thread overview]
Message-ID: <20160429201914.GA27596@roeck-us.net> (raw)
v4.4 (arm:allmodconfig):
drivers/mtd/nand/pxa3xx_nand.c: In function 'alloc_nand_resource':
drivers/mtd/nand/pxa3xx_nand.c:1753:7: error: 'np' undeclared
v4.5 (arm:allmodconfig, arm:pxa_defconfig):
drivers/dma/pxa_dma.c: In function 'pxad_probe':
drivers/dma/pxa_dma.c:1421:24: error: 'struct mmp_dma_platdata' has no member named 'nb_requestors'
There is also a qemu runtime failure with omap2plus_defconfig in v4.4.
[ 2.412322] omap_i2c 48070000.i2c: bus 0 rev3.3 at 2600 kHz
[ 2.417541] omap_i2c 48060000.i2c: bus 2 rev3.3 at 100 kHz
[ 2.429443]
[ 2.429534] =====================================
[ 2.429718] [ BUG: bad unlock balance detected! ]
[ 2.429962] 4.4.8-00025-gcd58757 #1 Not tainted
[ 2.430145] -------------------------------------
[ 2.430328] kworker/u2:0/6 is trying to release lock (&rdev->mutex) at:
[ 2.430694] [<c03b40e4>] regulator_set_voltage+0x40/0x54
[ 2.430877] but there are no more locks to release!
See logs at http://kerneltests.org/builders for details.
Please let me know if I need to bisect.
Thanks,
Guenter
next reply other threads:[~2016-04-29 20:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-29 20:19 Guenter Roeck [this message]
2016-05-03 13:35 ` (v4.4/v4.5)-stable-queue build and qemu failures (arm:allmodconfig, arm:pxa_defconfig, arm:omap2plus_defconfig) Adam Ford
2016-05-03 13:53 ` Guenter Roeck
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=20160429201914.GA27596@roeck-us.net \
--to=linux@roeck-us.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).