On Sun, Aug 19, 2012 at 12:23:38PM +0200, Bjørn Mork wrote:
Ming Lei tom.leim...@gmail.com writes:
On Fri, Aug 17, 2012 at 10:42 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Fri, Aug 17, 2012 at 10:38:16AM -0400, Alan Stern wrote:
On Fri, 17 Aug 2012, Ming Lei wrote:
Fengguang Wu fengguang...@intel.com writes:
@@ -779,6 +780,7 @@ static int usb_device_match(struct devic
intf = to_usb_interface(dev);
usb_drv = to_usb_driver(drv);
+ pr_info(%s: device %s, driver %s \n, __func__,
dev_name(dev), drv-name);
Bjørn Mork bj...@mork.no writes:
Fengguang Wu fengguang...@intel.com writes:
@@ -779,6 +780,7 @@ static int usb_device_match(struct devic
intf = to_usb_interface(dev);
usb_drv = to_usb_driver(drv);
+ pr_info(%s: device %s, driver %s \n, __func__,
Hi Bjørn,
-static const struct usb_device_id id_table[] __devinitconst = {
+static const struct usb_device_id id_table[] = {
Good catch! It magically fixed the oops. So that id_table was
freed sometime with __devinitconst?
There are some more usb_device_id .* __devinitconst users in the
On Fri, Aug 17, 2012 at 05:27:08PM +0800, Fengguang Wu wrote:
Hi Bjørn,
-static const struct usb_device_id id_table[] __devinitconst = {
+static const struct usb_device_id id_table[] = {
Good catch! It magically fixed the oops. So that id_table was
freed sometime with __devinitconst?
On Fri, Aug 17, 2012 at 6:24 PM, Fengguang Wu fengguang...@intel.com wrote:
On Fri, Aug 17, 2012 at 05:27:08PM +0800, Fengguang Wu wrote:
Hi Bjørn,
-static const struct usb_device_id id_table[] __devinitconst = {
+static const struct usb_device_id id_table[] = {
Good catch! It magically
On Fri, Aug 17, 2012 at 08:16:15PM +0800, Ming Lei wrote:
On Fri, Aug 17, 2012 at 6:24 PM, Fengguang Wu fengguang...@intel.com wrote:
On Fri, Aug 17, 2012 at 05:27:08PM +0800, Fengguang Wu wrote:
Hi Bjørn,
-static const struct usb_device_id id_table[] __devinitconst = {
+static const
On Fri, 17 Aug 2012, Ming Lei wrote:
But, if HOTPLUG is not enabled, should device_add() trigger driver probe
further after kernel init is completed? Or even devices should be allowed
to add into system?
Indeed, does it make any sense to have USB support at all if HOTPLUG
isn't enabled?
On Fri, Aug 17, 2012 at 10:38:16AM -0400, Alan Stern wrote:
On Fri, 17 Aug 2012, Ming Lei wrote:
But, if HOTPLUG is not enabled, should device_add() trigger driver probe
further after kernel init is completed? Or even devices should be allowed
to add into system?
Indeed, does it make
On Fri, Aug 17, 2012 at 10:42 PM, Greg Kroah-Hartman
gre...@linuxfoundation.org wrote:
On Fri, Aug 17, 2012 at 10:38:16AM -0400, Alan Stern wrote:
On Fri, 17 Aug 2012, Ming Lei wrote:
But, if HOTPLUG is not enabled, should device_add() trigger driver probe
further after kernel init is
On Sun, Aug 05, 2012 at 09:58:26AM -0700, Greg KH wrote:
On Sun, Aug 05, 2012 at 10:59:38AM +0800, Fengguang Wu wrote:
Hi all,
This line triggers an oops in kvm boot test:
usb_match_id():
== 748 for (; id-idVendor || id-idProduct ||
id-bDeviceClass ||
749
On Fri, Aug 17, 2012 at 10:00:46AM +0800, Fengguang Wu wrote:
On Sun, Aug 05, 2012 at 09:58:26AM -0700, Greg KH wrote:
On Sun, Aug 05, 2012 at 10:59:38AM +0800, Fengguang Wu wrote:
Hi all,
This line triggers an oops in kvm boot test:
usb_match_id():
== 748 for
On Sun, Aug 05, 2012 at 10:59:38AM +0800, Fengguang Wu wrote:
Hi all,
This line triggers an oops in kvm boot test:
usb_match_id():
== 748 for (; id-idVendor || id-idProduct || id-bDeviceClass
||
749id-bInterfaceClass || id-driver_info; id++) {
13 matches
Mail list logo
