From: Sasha Levin <sasha.levin@oracle.com>
To: Guenter Roeck <linux@roeck-us.net>, stable <stable@vger.kernel.org>
Cc: Youngmin Nam <ym0914@gmail.com>,
Gavin Shan <gwshan@linux.vnet.ibm.com>,
Alan Cox <alan@linux.intel.com>
Subject: Re: Build errors in v3.18-stable-queue
Date: Mon, 29 Feb 2016 19:24:33 -0500 [thread overview]
Message-ID: <56D4E141.5000100@oracle.com> (raw)
In-Reply-To: <56D2CFB3.1060202@roeck-us.net>
On 02/28/2016 05:45 AM, Guenter Roeck wrote:
> Current build results:
> total: 137 pass: 121 fail: 16
> Failed builds:
> arm:allmodconfig
> arm:omap2plus_defconfig
> arm:exynos_defconfig
> arm:s5pv210_defconfig
> powerpc:defconfig
> powerpc:allmodconfig
> powerpc:allnoconfig
> powerpc:ppc64e_defconfig
> powerpc:cell_defconfig
> powerpc:maple_defconfig
> powerpc:ppc6xx_defconfig
> powerpc:mpc83xx_defconfig
> powerpc:tqm8xx_defconfig
> powerpc:85xx/sbc8548_defconfig
> powerpc:83xx/mpc834x_mds_defconfig
> powerpc:86xx/sbc8641d_defconfig
>
> Culprits are listed below. Copying the patch authors for advice.
>
> Guenter
>
> ---
> powerpc:
>
> In file included from arch/powerpc/kernel/of_platform.c:30:0:
> ./arch/powerpc/include/asm/eeh.h:344:48: error: 'struct pci_dn' declared inside parameter list
>
> Culprit: "powerpc/eeh: Do probe on pci_dn"
>
> ---
> arm:
>
> drivers/pinctrl/samsung/pinctrl-samsung.c: In function 'samsung_gpio_set':
> drivers/pinctrl/samsung/pinctrl-samsung.c:551:9: error: implicit declaration of function 'gpiochip_get_data'
>
> Culprit: "pinctrl: samsung: fix SMP race condition"
>
> drivers/tty/serial/omap-serial.c: In function 'serial_omap_stop_tx':
> drivers/tty/serial/omap-serial.c:318:10: error: 'struct uart_port' has no member named 'rs485'
>
> drivers/tty/serial/omap-serial.c: In function 'serial_omap_probe':
> drivers/tty/serial/omap-serial.c:1683:10: error: 'struct uart_port' has no member named 'rs485_config'
>
> Culprit: "serial/omap: Use the rs485 functions on serial_core"
Thanks Guenter. I'll pull both of these out of 3.18 and 4.1 until we can get a proper
backport since it doesn't seem trivial.
Thanks,
Sasha
next prev parent reply other threads:[~2016-03-01 0:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:45 Build errors in v3.18-stable-queue Guenter Roeck
2016-03-01 0:24 ` Sasha Levin [this message]
2016-03-01 1:14 ` Gavin Shan
2016-03-01 2:47 ` Guenter Roeck
2016-03-01 5:06 ` Gavin Shan
2016-03-01 15:19 ` Sasha Levin
2016-03-01 23:17 ` Gavin Shan
2016-03-06 22:38 ` Gavin Shan
2016-03-02 4:31 ` Guenter Roeck
2016-03-01 11:12 ` Youngmin Nam
2016-03-01 15:18 ` Sasha Levin
-- strict thread matches above, loose matches on Subject: below --
2015-08-25 19:24 build " 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=56D4E141.5000100@oracle.com \
--to=sasha.levin@oracle.com \
--cc=alan@linux.intel.com \
--cc=gwshan@linux.vnet.ibm.com \
--cc=linux@roeck-us.net \
--cc=stable@vger.kernel.org \
--cc=ym0914@gmail.com \
/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.