Date: Tue, 11 Apr 2017 06:42:36 +0200
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-kernel@vger.kernel.org,
        Linus Torvalds <torvalds@linux-foundation.org>,
        akpm@linux-foundation.org, shuahkh@osg.samsung.com,
        patches@kernelci.org, ben.hutchings@codethink.co.uk,
        stable@vger.kernel.org, Tony Lindgren <tony@atomide.com>,
        Sean Young <sean@mess.org>
Subject: Re: [PATCH 4.9 000/152] 4.9.22-stable review
Message-ID: <20170411044236.GB31847@kroah.com>
References: <20170410164159.934755016@linuxfoundation.org>
 <38bcb13d-1a22-3f52-21a6-c91f83631a72@roeck-us.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <38bcb13d-1a22-3f52-21a6-c91f83631a72@roeck-us.net>
User-Agent: Mutt/1.8.0 (2017-02-23)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 3285
Lines: 84

On Mon, Apr 10, 2017 at 08:07:17PM -0700, Guenter Roeck wrote:
> On 04/10/2017 09:40 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.9.22 release.
> > There are 152 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 Apr 12 16:41:34 UTC 2017.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
> 	total: 149 pass: 146 fail: 3
> Failed builds:
> 	arm:allmodconfig
> 	arm:omap2plus_defconfig
> 	arm64:allmodconfig
> 
> Qemu test results:
> 	total: 122 pass: 103 fail: 19
> Failed tests:
> 	arm:beagle:multi_v7_defconfig:omap3-beagle
> 	arm:beaglexm:multi_v7_defconfig:omap3-beagle-xm
> 	arm:overo:multi_v7_defconfig:omap3-overo-tobi
> 	arm:sabrelite:multi_v7_defconfig:imx6dl-sabrelite
> 	arm:vexpress-a9:multi_v7_defconfig:vexpress-v2p-ca9
> 	arm:vexpress-a15:multi_v7_defconfig:vexpress-v2p-ca15-tc1
> 	arm:vexpress-a15-a7:multi_v7_defconfig:vexpress-v2p-ca15_a7
> 	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc702
> 	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zc706
> 	arm:xilinx-zynq-a9:multi_v7_defconfig:zynq-zed
> 	arm:midway:multi_v7_defconfig:ecx-2000
> 	arm:smdkc210:multi_v7_defconfig:exynos4210-smdkv310
> 	arm:beagle:omap2plus_defconfig:omap3-beagle
> 	arm:beaglexm:omap2plus_defconfig:omap3-beagle-xm
> 	arm:overo:omap2plus_defconfig:omap3-overo-tobi
> 	arm64:virt:smp:defconfig
> 	arm64:xlnx-ep108:smp:defconfig:zynqmp-ep108
> 	arm64:virt:nosmp:defconfig
> 	arm64:xlnx-ep108:nosmp:defconfig:zynqmp-ep108
> 
> As reported earlier, the arm64 builds fail with
> 
> Building arm64:virt:nosmp:defconfig ... failed
> ------------
> Error log:
> arch/arm64/Makefile:23: ld does not support --fix-cortex-a53-843419; kernel may be susceptible to erratum
> arch/arm64/kernel/pci.c: In function ‘pci_acpi_setup_ecam_mapping’:
> arch/arm64/kernel/pci.c:139:9: error: implicit declaration of function ‘acpi_resource_consumer’
>   adev = acpi_resource_consumer(&cfgres);
> ...
> drivers/pci/host/pcie-hisi.c: In function ‘hisi_pcie_init’:
> drivers/pci/host/pcie-hisi.c:94:8: error: implicit declaration of function ‘acpi_get_rc_resources’
> 
> ---
> 
> The arm builds fail as follows.
> 
> Building arm:overo:omap2plus_defconfig:omap3-overo-tobi ... failed
> ------------
> Error log:
> In file included from arch/arm/mach-omap2/pdata-quirks.c:15:0:
> arch/arm/mach-omap2/pdata-quirks.c:537:49: error: 'rx51_ir_data' undeclared here (not in a function)
>   OF_DEV_AUXDATA("nokia,n900-ir", 0, "n900-ir", &rx51_ir_data),
>                                                  ^
> ./include/linux/of_platform.h:52:21: note: in definition of macro 'OF_DEV_AUXDATA'
>     .platform_data = _pdata }
>                      ^
> make[1]: *** [arch/arm/mach-omap2/pdata-quirks.o] Error 1
> 
> I am a bit lost here. Reverting
> 
> f2ea7a5c3730 rx51: broken build
> 
> fixes the problem, but is supposed to accomplish the opposite. You'll need to drop
> that patch, or maybe even better drop
> 
> 375a81645446 ARM: OMAP2+: Fix init for multiple quirks for the same SoC
> 
> as well and let the authors [copied] sort this out.

Good idea, both now dropped, thanks.

greg k-h