ping?

Just saw another failing report
(http://status.armcloud.us/boot/zynq-zc702/job/stable/kernel/v3.10.55/defconfig/arm-multi_v7_defconfig/).

        Thanks,
        Sören

On Mon, 2014-09-08 at 09:41AM -0700, Sören Brinkmann wrote:
> Hi Greg,
> 
> Kevin's boot tests report Zynq failing with kernel 3.10.54 (see
> forwarded email below). The issue is simply the UART driver for
> Zynq missing from the defconfig. That driver has been added to
> the defconfing in commit 'arm: multi_v7_defconfig: Enable Zynq
> UART driver' (90de827b9c238f8d8209bc7adc70190575514315).
> Could we get that applied to the stable branch, please (I include
> a patch at the end of the email)?
> If not, Kevin, please go ahead and blacklist Zynq from 3.10.x testing.
> 
>       Thanks,
>       Sören
> 
> ----- Forwarded message from Kevin Hilman <[email protected]> -----
> Date: Sun, 7 Sep 2014 20:35:21 -0700
> From: Kevin Hilman <[email protected]>
> To: Sören Brinkmann <[email protected]>
> CC: Kevin's boot bot <[email protected]>, 
> [email protected], "[email protected]" 
> <[email protected]>
> Subject: Re: stable boot: 27 boots: 26 pass, 1 fail (v3.10.54)
> 
> On Sun, Sep 7, 2014 at 2:08 PM, Sören Brinkmann <[email protected]> 
> wrote:
> > Hi Kevin,
> >
> > On Sat, 2014-09-06 at 03:14AM +0000, Kevin's boot bot wrote:
> >> Status report database:  
> >> http://status.armcloud.us/boot/all/job/stable/kernel/v3.10.54/
> >>
> >> Tree/Branch: stable
> >> Git describe: v3.10.54
> >> Failed boot tests
> >> =================
> >>                   zynq-zc702:     FAIL:    arm-multi_v7_defconfig
> >>                                   
> >> http://armcloud.us/kernel-ci/stable/v3.10.54/arm-multi_v7_defconfig/boot-zynq-zc702.html
> >
> > The defconfig in 3.10 is missing some Zynq stuff. In particular 'arm:
> > multi_v7_defconfig: Enable Zynq UART driver'
> > (90de827b9c238f8d8209bc7adc70190575514315). Cherry-picking that into
> > 3.10.54 let's me boot the board with console output.
> 
> Would you like to send a request to stable folks to pick that into the
> stable kernel?  Or, I could blacklist zync from stable-3.10 testing.
> Let me know.
> 
> Kevin
> 
> ----- End forwarded message -----
> 
> --------------8<---------------------8<--------------------------8<-------------
> Date: Wed, 19 Jun 2013 10:53:03 -0700
> Subject: [PATCH] arm: multi_v7_defconfig: Enable Zynq UART driver
> 
> commit 90de827b9c238f8d8209bc7adc70190575514315 upstream.
> 
> Signed-off-by: Soren Brinkmann <[email protected]>
> Signed-off-by: Michal Simek <[email protected]>
> ---
>  arch/arm/configs/multi_v7_defconfig | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/arch/arm/configs/multi_v7_defconfig 
> b/arch/arm/configs/multi_v7_defconfig
> index 9ce8ba1a1433..adb9aa5c88c7 100644
> --- a/arch/arm/configs/multi_v7_defconfig
> +++ b/arch/arm/configs/multi_v7_defconfig
> @@ -48,6 +48,8 @@ CONFIG_SERIAL_SIRFSOC=y
>  CONFIG_SERIAL_SIRFSOC_CONSOLE=y
>  CONFIG_SERIAL_VT8500=y
>  CONFIG_SERIAL_VT8500_CONSOLE=y
> +CONFIG_SERIAL_XILINX_PS_UART=y
> +CONFIG_SERIAL_XILINX_PS_UART_CONSOLE=y
>  CONFIG_IPMI_HANDLER=y
>  CONFIG_IPMI_SI=y
>  CONFIG_I2C=y
> -- 
> 2.1.0.1.g27b9230
> 
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to