2
0
mirror of https://github.com/edk2-porting/linux-next.git synced 2024-12-16 17:23:55 +08:00
linux-next/arch/cris
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>
2008-01-24 20:40:30 -08:00
..
arch-v10 CRIS: add missed local_irq_restore call 2008-01-21 19:39:41 -08:00
arch-v32 Kobject: the cris iop_fw_load.c code is broken 2008-01-24 20:40:30 -08:00
kernel cris build fixes: fix crisksyms.c 2007-11-14 18:45:46 -08:00
mm spelling fixes: arch/cris/ 2007-10-20 01:08:50 +02:00
defconfig CRIS: remove MTD_AMSTD and MTD_OBSOLETE_CHIPS take two 2007-11-14 18:45:46 -08:00
Kconfig cris build fixes: corrected and improved NMI and IRQ handling 2007-11-14 18:45:45 -08:00
Kconfig.debug [PATCH] arch/cris/Kconfig.debug: use lib/Kconfig.debug 2005-09-05 00:06:19 -07:00
Makefile kbuild: enable 'make AFLAGS=...' to add additional options to AS 2007-10-15 21:59:31 +02:00