From: khilman@ti•com (Kevin Hilman)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot
Date: Tue, 28 Feb 2012 10:23:45 -0800 [thread overview]
Message-ID: <87y5rmyfym.fsf@ti.com> (raw)
In-Reply-To: <20120228172851.GA13653@kroah.com> (Greg KH's message of "Tue, 28 Feb 2012 09:28:51 -0800")
Greg KH <gregkh@linuxfoundation•org> writes:
> 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?
It is needed for 3.3-final.
Thanks,
Kevin
next prev parent reply other threads:[~2012-02-28 18:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 2:50 [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver Paul Walmsley
2012-01-26 2:50 ` [PATCH v2 1/3] tty: serial: OMAP: use a 1-byte RX FIFO threshold in PIO mode Paul Walmsley
2012-01-26 2:50 ` [PATCH 2/3] tty: serial: OMAP: block idle while the UART is transferring data " Paul Walmsley
2012-01-26 2:58 ` Paul Walmsley
2012-01-27 7:23 ` Govindraj
2012-02-20 12:35 ` Cousson, Benoit
2012-02-21 22:02 ` Paul Walmsley
2012-02-24 14:35 ` Cousson, Benoit
2012-02-28 17:13 ` Paul Walmsley
2012-02-28 17:22 ` [PATCH] tty: serial: OMAP: Fix oops due to NULL pdata in DT boot Cousson, Benoit
2012-02-28 17:28 ` Greg KH
2012-02-28 18:23 ` Kevin Hilman [this message]
2012-01-26 2:50 ` [PATCH v2 3/3] tty: serial: omap-serial: wakeup latency constraint is in microseconds, not milliseconds Paul Walmsley
2012-01-27 7:19 ` Govindraj
2012-01-30 19:13 ` [PATCH v2 0/3] tty: serial: OMAP: work around broken IP block, driver Kevin Hilman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y5rmyfym.fsf@ti.com \
--to=khilman@ti$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox