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

    staging:serqt_usb2: Fix sparse warning restricted __le16 degrades to integer

to the 3.10-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:
     
staging-serqt_usb2-fix-sparse-warning-restricted-__le16-degrades-to-integer.patch
and it can be found in the queue-3.10 subdirectory.

If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.


>From abe5d64d1a74195a44cd14624f8178b9f48b7cc7 Mon Sep 17 00:00:00 2001
From: Himangi Saraogi <himangi...@gmail.com>
Date: Wed, 5 Mar 2014 04:59:57 +0530
Subject: staging:serqt_usb2: Fix sparse warning restricted __le16 degrades to 
integer

From: Himangi Saraogi <himangi...@gmail.com>

commit abe5d64d1a74195a44cd14624f8178b9f48b7cc7 upstream.

This patch fixes the following sparse warning :
drivers/staging/serqt_usb2/serqt_usb2.c:727:40: warning: restricted __le16 
degrades to integer

Signed-off-by: Himangi Saraogi <himangi...@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>

---
 drivers/staging/serqt_usb2/serqt_usb2.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/staging/serqt_usb2/serqt_usb2.c
+++ b/drivers/staging/serqt_usb2/serqt_usb2.c
@@ -725,7 +725,7 @@ static int qt_startup(struct usb_serial
                goto startup_error;
        }
 
-       switch (serial->dev->descriptor.idProduct) {
+       switch (le16_to_cpu(serial->dev->descriptor.idProduct)) {
        case QUATECH_DSU100:
        case QUATECH_QSU100:
        case QUATECH_ESU100A:


Patches currently in stable-queue which might be from himangi...@gmail.com are

queue-3.10/staging-serqt_usb2-fix-sparse-warning-restricted-__le16-degrades-to-integer.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to