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

    usb: musb: da8xx: Fix build breakage due to typo

to the 3.8-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:
     usb-musb-da8xx-fix-build-breakage-due-to-typo.patch
and it can be found in the queue-3.8 subdirectory.

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


>From db9e51617faad3a54d10b7cb340a82688ec0232d Mon Sep 17 00:00:00 2001
From: Mikhail Kshevetskiy <[email protected]>
Date: Thu, 14 Mar 2013 10:18:29 +0100
Subject: usb: musb: da8xx: Fix build breakage due to typo

From: Mikhail Kshevetskiy <[email protected]>

commit db9e51617faad3a54d10b7cb340a82688ec0232d upstream.

Commit 032ec49f5351e9cb242b1a1c367d14415043ab95 (usb: musb: drop useless
board_mode usage) introduced a typo that breaks the build.

Signed-off-by: Mikhail Kshevetskiy <[email protected]>

[ Fixed commit message ]

Signed-off-by: Michael Riesch <[email protected]>
Cc: Mikhail Kshevetskiy <[email protected]>
Cc: Sergei Shtylyov <[email protected]>
Signed-off-by: Felipe Balbi <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/usb/musb/da8xx.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/usb/musb/da8xx.c
+++ b/drivers/usb/musb/da8xx.c
@@ -327,7 +327,7 @@ static irqreturn_t da8xx_musb_interrupt(
                u8 devctl = musb_readb(mregs, MUSB_DEVCTL);
                int err;
 
-               err = musb->int_usb & USB_INTR_VBUSERROR;
+               err = musb->int_usb & MUSB_INTR_VBUSERROR;
                if (err) {
                        /*
                         * The Mentor core doesn't debounce VBUS as needed


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

queue-3.8/usb-musb-da8xx-fix-build-breakage-due-to-typo.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