This is a note to let you know that I've just added the patch titled

    pch_uart: Fix missing break for 16 byte fifo

to the 3.5-stable tree which can be found at:
    
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
     pch_uart-fix-missing-break-for-16-byte-fifo.patch
and it can be found in the queue-3.5 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.


>From 9bc03743fff0770dc5a5324ba92e67cc377f16ca Mon Sep 17 00:00:00 2001
From: Alan Cox <[email protected]>
Date: Mon, 2 Jul 2012 18:51:38 +0100
Subject: pch_uart: Fix missing break for 16 byte fifo

From: Alan Cox <[email protected]>

commit 9bc03743fff0770dc5a5324ba92e67cc377f16ca upstream.

Otherwise we fall back to the wrong value.

Reported-by: <[email protected]>
Resolves-bug: https://bugzilla.kernel.org/show_bug.cgi?id=44091
Signed-off-by: Alan Cox <[email protected]>
Signed-off-by: Tomoya MORINAGA <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/tty/serial/pch_uart.c |    1 +
 1 file changed, 1 insertion(+)

--- a/drivers/tty/serial/pch_uart.c
+++ b/drivers/tty/serial/pch_uart.c
@@ -1263,6 +1263,7 @@ static int pch_uart_startup(struct uart_
                break;
        case 16:
                fifo_size = PCH_UART_HAL_FIFO16;
+               break;
        case 1:
        default:
                fifo_size = PCH_UART_HAL_FIFO_DIS;


Patches currently in stable-queue which might be from [email protected] are

queue-3.5/gma500-fix-regression-on-oaktrail-devices.patch
queue-3.5/dj-memory-scribble-in-logi_dj.patch
queue-3.5/usb-ftdi_sio-do-not-claim-cdc-acm-function.patch
queue-3.5/ahci-add-alternate-identifier-for-the-88se9172.patch
queue-3.5/pch_uart-fix-missing-break-for-16-byte-fifo.patch
queue-3.5/pch_uart-fix-parity-setting-issue.patch
queue-3.5/pch_uart-fix-rx-error-interrupt-setting-issue.patch
--
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