serial-omap regression?

[Kevin Hilman <khilman@deeprootsystems.com>]

Hi Felipe,

I just noticed today that one of my boards (3530/Overo) was not making
it to the console when using an Debian rootfs (nfsroot) but works fine
with my basic busybox initramfs.  Basically, it hangs somewhere between
finishing the userspace init and launching the login shell.

git bisect ended up pointing the finger at a patch in the OMAP serial
series[1].  I didn't debug this any further.  Any ideas?

Kevin


72256cbd13904d4b4dbb16f5ec83a3293bb292c5 is the first bad commit
commit 72256cbd13904d4b4dbb16f5ec83a3293bb292c5
Author: Felipe Balbi <balbi@ti.com>
Date:   Thu Sep 6 15:45:24 2012 +0300

    serial: omap: refactor receive_chars() into rdi/rlsi handlers
    
    receive_chars() was getting too big and too difficult
    to follow. By splitting it into separate RDI and RSLI
    handlers, we have smaller functions which are easy
    to understand and only touch the pieces which they need
    to touch.
    
    Tested-by: Shubhrajyoti D <shubhrajyoti@ti.com>
    Acked-by: Santosh Shilimkar <santosh.shilimkar@ti.com>
    Signed-off-by: Felipe Balbi <balbi@ti.com>
    Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

:040000 040000 69585356cd524953305cfba7d219cd65430a4067 ffdc0c05004afe8b73c1f2c0ba41e412c1faf5f4 M	drivers