Jean Delvare a456b7023e dev_printk and new-style class devices ... As the new-style class devices (as opposed to old-style struct class_device) are becoming more widely used, I noticed that the dev_printk-based functions are not working properly with these. New-style class devices have no driver nor bus, almost by definition, and as a result dev_driver_string(), which is used as the first parameter of dev_printk, resolves to an empty string. This causes entries like the following to show in my logs: i2c-2: adapter [SMBus stub driver] registered Notice the unaesthetical leading whitespace. In order to fix this problem, I suggest that we extend dev_driver_string to deal with new-style class devices: Signed-off-by: Jean Delvare <khali@linux-fr.org> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>		2007-04-27 10:57:28 -07:00
..
power	[PATCH] PM: use kobject_name() to access kobject names	2007-04-11 15:39:39 -07:00
attribute_container.c
base.h
bus.c
class.c	driver core: fix namespace issue with devices assigned to classes	2007-04-27 10:57:28 -07:00
core.c	dev_printk and new-style class devices	2007-04-27 10:57:28 -07:00
cpu.c	Replace remaining references to "driverfs" with "sysfs".	2007-02-17 19:13:42 +01:00
dd.c
devres.c
dma-mapping.c
dmapool.c
driver.c	driver core: do not wait unnecessarily in driver_unregister()	2007-04-01 10:54:13 -07:00
firmware_class.c
firmware.c
hypervisor.c
init.c
isa.c
Kconfig
Makefile
map.c
memory.c
node.c	Replace remaining references to "driverfs" with "sysfs".	2007-02-17 19:13:42 +01:00
platform.c
sys.c
topology.c
transport_class.c