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

    media: cx88: Fix regression: CX88_AUDIO_WM8775 can't be 0

to the 3.11-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:
     media-cx88-fix-regression-cx88_audio_wm8775-can-t-be-0.patch
and it can be found in the queue-3.11 subdirectory.

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


>From f66b2a1c7f2ae3fb0d5b67d07ab4f5055fd3cf16 Mon Sep 17 00:00:00 2001
From: Hans Verkuil <[email protected]>
Date: Tue, 27 Aug 2013 04:27:57 -0300
Subject: media: cx88: Fix regression: CX88_AUDIO_WM8775 can't be 0

From: Hans Verkuil <[email protected]>

commit f66b2a1c7f2ae3fb0d5b67d07ab4f5055fd3cf16 upstream.

Cards using the wm8775 specify that in their card struct. Those that do not
use it leave the audio_chip field to 0. Unfortunately, the CX88_AUDIO_WM8775
enum is 0 as well, so boards that do not have the wm8775 still try to load
and use that driver. Change it to 1 to fix this.
This regression was introduced in commit 
facd23664f1d63c33fbc6da52261c8548ed3fbd4.

Signed-off-by: Hans Verkuil <[email protected]>
Reported-by: Knut Petersen <[email protected]>
Tested-by: Knut Petersen <[email protected]>
Signed-off-by: Mauro Carvalho Chehab <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>

---
 drivers/media/pci/cx88/cx88.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- a/drivers/media/pci/cx88/cx88.h
+++ b/drivers/media/pci/cx88/cx88.h
@@ -259,7 +259,7 @@ struct cx88_input {
 };
 
 enum cx88_audio_chip {
-       CX88_AUDIO_WM8775,
+       CX88_AUDIO_WM8775 = 1,
        CX88_AUDIO_TVAUDIO,
 };
 


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

queue-3.11/media-cx88-fix-regression-cx88_audio_wm8775-can-t-be-0.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