Re: [PATCH 3.14 00/79] 3.14.37-stable review

[Greg Kroah-Hartman]

On Wed, Mar 25, 2015 at 06:07:45AM -0700, Guenter Roeck wrote:
> On 03/25/2015 06:03 AM, Guenter Roeck wrote:
> >On 03/25/2015 01:30 AM, Greg Kroah-Hartman wrote:
> >>On Tue, Mar 24, 2015 at 07:50:07PM -0700, Guenter Roeck wrote:
> >>>On 03/24/2015 08:45 AM, Greg Kroah-Hartman wrote:
> >>>>This is the start of the stable review cycle for the 3.14.37 release.
> >>>>There are 79 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 Thu Mar 26 15:43:19 UTC 2015.
> >>>>Anything received after that time might be too late.
> >>>>
> >>>
> >>>Build results:
> >>>    total: 123 pass: 120 fail: 3
> >>>Failed builds:
> >>>    arm:imx_v6_v7_defconfig
> >>>    arm:multi_v7_defconfig
> >>>    arm:imx_v4_v5_defconfig
> >>>
> >>>Qemu test results:
> >>>    total: 30 pass: 30 fail: 0
> >>>
> >>>--------------
> >>>Build error log:
> >>>
> >>>ERROR (phandle_references): Reference to non-existent node or label "swbst_reg"
> >>>ERROR (phandle_references): Reference to non-existent node or label "swbst_reg"
> >>>ERROR: Input tree has errors, aborting (use -f to force output)
> >>>make[1]: *** [arch/arm/boot/dts/imx6dl-sabresd.dtb] Error 2
> >>>make[1]: *** Waiting for unfinished jobs....
> >>>make: *** [dtbs] Error 2
> >>>
> >>>Caused by 'ARM: imx6qdl-sabresd: set swbst_reg as vbus's parent reg'
> >>>and 'ARM: imx6sl-evk: set swbst_reg as vbus's parent reg'.
> >>>
> >>>swbst_reg was only introduced with commit 4b444bb82fa8 ("ARM: dts:
> >>>imx6qdl-sabresd: Add PFUZE100 support"). Unfortunately, that patch
> >>>does not apply cleanly.
> >>
> >>Thanks, I've now dropped that patch from the queue.
> >>
> >
> >Two patches, not just one.
> >
> 
> Yep, you still need to drop 'ARM: imx6sl-evk: set swbst_reg as vbus's parent reg'.

Thanks, now dropped.

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/