[PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot

[PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver · paul@pwsan.com (Paul Walmsley) · 2012-01-26
[PATCH v2 1/3] tty: serial: OMAP: use a 1-byte RX FIFO threshold in PIO mode · paul@pwsan.com (Paul Walmsley) · 2012-01-26
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · paul@pwsan.com (Paul Walmsley) · 2012-01-26
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · paul@pwsan.com (Paul Walmsley) · 2012-01-26
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · Govindraj <hidden> · 2012-01-27
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · Cousson, Benoit <hidden> · 2012-02-20
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · paul@pwsan.com (Paul Walmsley) · 2012-02-21
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · Cousson, Benoit <hidden> · 2012-02-24
[PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data in PIO mode · paul@pwsan.com (Paul Walmsley) · 2012-02-28
[PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot · Cousson, Benoit <hidden> · 2012-02-28
[PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot · gregkh@linuxfoundation.org (Greg KH) · 2012-02-28
[PATCH v2 3/3] tty: serial: omap-serial: wakeup latency constraint is in microseconds, not milliseconds · paul@pwsan.com (Paul Walmsley) · 2012-01-26
[PATCH v2 3/3] tty: serial: omap-serial: wakeup latency constraint is in microseconds, not milliseconds · Govindraj <hidden> · 2012-01-27

DORMANTno replies

From: gregkh@linuxfoundation.org (Greg KH)
Date: 2012-02-28 17:28:51
Also in: linux-omap, linux-serial

On Tue, Feb 28, 2012 at 06:22:12PM +0100, Cousson, Benoit wrote:

The following commit: be4b0281956c5cae4f63f31f11d07625a6988766
(tty: serial: OMAP: block idle while the UART is transferring data in PIO mode),
is introducing an oops if OMAP is booted using device tree blob because
the pdata will not be initialized.

Is that something that happens today on systems?  Does this need to go
in for 3.3-final, or can it wait for 3.4?

thanks,

greg k-h

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help