lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 Mar 2011 02:55:53 +0100
From:	Alexander Holler <holler@...oftware.de>
To:	balbi@...com
CC:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: musb as module broken in 2.6.38

Hello,

in commit dc09886bfa781e2b442301116c18199519e36f0f the name of the 
platform-driver was splitted and musb-omap2430 is used for several 
boards (arch/arm/mach-omap2/usb-musb.c).

But musb_hdrc still uses musb-hdrc as name when platform_driver_probe() 
is called. The result is that loading the driver (when build as a 
module) doesn't work anymore (it doesn't find the platform-device).

Do I miss something or was something forgotten when the glue-layers for 
musb got introduced?

(The driver still works when linked into the kernel, but is 
disfunctional when build as a module.)

Regards,

Alexander Holler
--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ