summaryrefslogtreecommitdiffstats
path: root/arch/sh64/Kconfig.debug
diff options
context:
space:
mode:
authorGreg Kroah-Hartman <gregkh@suse.de>2007-12-18 07:05:35 +0100
committerGreg Kroah-Hartman <gregkh@suse.de>2008-01-25 05:40:30 +0100
commit52840bd628707979b5bbcce3c506786d3a69dba0 (patch)
tree15c9b60fa5884e62706fd86defec2ab749a24bfa /arch/sh64/Kconfig.debug
parentKobject: change arch/x86/kernel/cpu/mcheck/mce_amd_64.c to use kobject_init_a... (diff)
downloadlinux-52840bd628707979b5bbcce3c506786d3a69dba0.tar.xz
linux-52840bd628707979b5bbcce3c506786d3a69dba0.zip
Kobject: the cris iop_fw_load.c code is broken
This code is really really really broken. So much so that it's almost impossible to fix with a simple patch, so just comment out the offending registration with the kobject core, and mark the driver as broken. The problem is that the code is trying to register a "raw" struct device, which is not allowed. struct device is only for use within the driver model. This is being done to try to use the firmware layer which wants a struct device. To properly fix this, use something easy, like a platform device, which is a struct device and can be used for this kind of thing. Cc: Mikael Starvik <starvik@axis.com> Cc: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'arch/sh64/Kconfig.debug')
0 files changed, 0 insertions, 0 deletions