You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Greg Kroah-Hartman 52840bd628 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>		17 years ago
..
pci	some kmalloc/memset ->kzalloc (tree wide)	18 years ago
Kconfig	ide: move CONFIG_IDE_ETRAX to drivers/ide/Kconfig	17 years ago
Makefile	…
axisflashmap.c	CRIS: remove MTD_AMSTD and MTD_OBSOLETE_CHIPS take two	17 years ago
cryptocop.c	CRIS: replace old-style member inits with designated inits	18 years ago
gpio.c	…
i2c.c	spelling fixes: arch/cris/	18 years ago
i2c.h	…
iop_fw_load.c	Kobject: the cris iop_fw_load.c code is broken	17 years ago
nandflash.c	spelling fixes: arch/cris/	18 years ago
pcf8563.c	Fix misspellings of "system", "controller", "interrupt" and "necessary".	18 years ago
sync_serial.c	cris: ARRAY_SIZE() cleanup	17 years ago