[<prev] [next>] [day] [month] [year] [list]
Message-ID: <CAGsJ_4xjYxXgQLDka0J3M3+FSHVQ2LmvgcWKUiqdhQ20gxCFsw@mail.gmail.com>
Date: Thu, 29 May 2014 20:29:20 +0800
From: Barry Song <21cnbao@...il.com>
To: sfr@...b.auug.org.au,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Qipan Li <Qipan.Li@....com>
Cc: LKML <linux-kernel@...r.kernel.org>, linux-next@...r.kernel.org,
DL-SHA-WorkGroupLinux <workgroup.linux@....com>
Subject: Re: linux-next: build failure after merge of the tty tree
2014-05-29 20:18 GMT+08:00 Barry Song <Barry.Song@....com>:
> From: Stephen Rothwell [sfr@...b.auug.org.au]
> Sent: Thursday, May 29, 2014 15:28
> To: Greg KH
> Cc: linux-next@...r.kernel.org; linux-kernel@...r.kernel.org; Qipan Li; Barry Song
> Subject: linux-next: build failure after merge of the tty tree
>
> Hi Greg,
>
> After merging the tty tree, today's linux-next build (arm
> multi_v7_defconfig) failed like this:
>
> drivers/tty/serial/sirfsoc_uart.c: In function 'sirfsoc_uart_rx_dma_complete_tl':
> drivers/tty/serial/sirfsoc_uart.c:707:2: error: 'struct uart_port' has no member named 'rx_lock'
>
> Caused by commit 07d410e06463 ("serial: sirf: fix spinlock deadlock
> issue"). Did anyone even build test this? Much less test that it fixed
> the deadlock ... :-(
>
Stephen, it is my fault. qipan did a strange mis-operation when he
prepared this patch and i didn't double-confirm it.
but the patch did have been tested on real hardware to fix the
deadlock issue. it is not a patch without test.
the build issue has been fixed in another thread: [PATCH tty-next]
serial: sirf: Fix compilation failure
https://lkml.org/lkml/2014/5/29/476
i am very sorry for this as the related platform maintainer. i didn't
control this well and missed to do a double build for this. again, i
am very sorry!
> I have used the tty tree from next-20140528 for today.
> --
> Cheers,
> Stephen Rothwell sfr@...b.auug.org.au
>
-barry
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists