[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120912233541.903642401@linuxfoundation.org>
Date: Wed, 12 Sep 2012 16:35:44 -0700
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-kernel@...r.kernel.org, stable@...r.kernel.org
Cc: Greg KH <gregkh@...uxfoundation.org>,
Fengguang Wu <fengguang.wu@...el.com>,
Bjørn Mork <bjorn@...k.no>,
Forest Bond <forest@...ttletooquiet.net>,
Marcos Paulo de Souza <marcos.souza.org@...il.com>,
"David S. Miller" <davem@...emloft.net>,
Jesper Juhl <jj@...osbits.net>, Jiri Pirko <jpirko@...hat.com>
Subject: [ 01/85] USB: vt6656: remove __devinit* from the struct usb_device_id table
From: Greg KH <gregkh@...uxfoundation.org>
3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
commit 4d088876f24887cd15a29db923f5f37db6a99f21 upstream.
This structure needs to always stick around, even if CONFIG_HOTPLUG
is disabled, otherwise we can oops when trying to probe a device that
was added after the structure is thrown away.
Thanks to Fengguang Wu and Bjørn Mork for tracking this issue down.
Reported-by: Fengguang Wu <fengguang.wu@...el.com>
Reported-by: Bjørn Mork <bjorn@...k.no>
CC: Forest Bond <forest@...ttletooquiet.net>
CC: Marcos Paulo de Souza <marcos.souza.org@...il.com>
CC: "David S. Miller" <davem@...emloft.net>
CC: Jesper Juhl <jj@...osbits.net>
CC: Jiri Pirko <jpirko@...hat.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
---
drivers/staging/vt6656/main_usb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/vt6656/main_usb.c
+++ b/drivers/staging/vt6656/main_usb.c
@@ -222,7 +222,7 @@ DEVICE_PARAM(b80211hEnable, "802.11h mod
// Static vars definitions
//
-static struct usb_device_id vt6656_table[] __devinitdata = {
+static struct usb_device_id vt6656_table[] = {
{USB_DEVICE(VNT_USB_VENDOR_ID, VNT_USB_PRODUCT_ID)},
{}
};
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists