linux/drivers/staging, branch v2.6.28

STAGING: Move staging drivers back to staging-specific menu

2008-12-17T19:23:07Z

Signed-off-by: Dmitry Baryshkov Signed-off-by: Greg Kroah-Hartman

Don't ask twice about not including staging drivers

2008-11-09T20:47:04Z

The "Exclude staging drivers" question is there so that we don't build staging drivers for allyesconfig or allnoconfig settings, but it's very irritating when you've already said "no" to staging drivers earlier. There is absolutely no point in declining twice - once you've declined the staging drivers, you're done. So make the second question depend on the first question having been answered in the affirmative. Signed-off-by: Linus Torvalds

Staging: make usbip depend on CONFIG_NET

2008-11-08T06:05:18Z

Thanks to Randy Dunlap for finding this problem. Reported-by: Randy Dunlap Signed-off-by: Greg Kroah-Hartman

Staging: only build the tree if we really want to

2008-11-08T06:05:18Z

This Kconfig change allows the common 'make allmodconfig' and 'make allyesconfig' build options to skip the staging tree, which is probably what you want to have happen anyway. This makes the linux-next developer's life a lot easier so he doesn't have to worry about changes that break the staging tree, that's for me to worry about... Signed-off-by: Greg Kroah-Hartman

drivers: remove duplicated #include

2008-11-04T16:18:19Z

Signed-off-by: Jianjun Kong Signed-off-by: Linus Torvalds

saner FASYNC handling on file close

2008-11-01T16:49:46Z

As it is, all instances of ->release() for files that have ->fasync() need to remember to evict file from fasync lists; forgetting that creates a hole and we actually have a bunch that *does* forget. So let's keep our lives simple - let __fput() check FASYNC in file->f_flags and call ->fasync() there if it's been set. And lose that crap in ->release() instances - leaving it there is still valid, but we don't have to bother anymore. Signed-off-by: Al Viro Signed-off-by: Linus Torvalds

staging: pcc_acpi: delete obsolete driver

2008-10-23T19:31:09Z

pcc_acpi is based on an old version of drivers/misc/panasonic-laptop.c Signed-off-by: Len Brown

pcc-acpi: fix compile with new stricter ACPI types

2008-10-23T18:54:08Z

This was another merge problem that wasn't a data conflict, but due to independent changes in two branches that just didn't work together. The pcc-acpi staging driver used acpi_driver_data(device) = hotkey; to set driver data, but the ACPI merge made that invalid in commit db89b4f0dbab837d0f3de2c3e9427a8d5393afa3 ("ACPI: catch calls of acpi_driver_data on pointer of wrong type"), and now you're supposed to just do. device->driver_data = hotkey; instead. Fix it up. Signed-off-by: Linus Torvalds

Staging: usbip: fix build warning on 64bit kernels

2008-10-22T16:56:40Z

Signed-off-by: Greg Kroah-Hartman

Staging: me4000: remove some compiler warnings

2008-10-22T16:56:40Z

Signed-off-by: Greg Kroah-Hartman