[GIT PATCH] STAGING fixes for 2.6.36-git
From: Greg KH
Date: Fri Sep 03 2010 - 22:10:56 EST
Here are a bunch of tiny staging bugfixes and a few new device ids for
your 2.6.36-git tree.
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/gregkh/staging-2.6.git/
All of these patches have been in the linux-next and mm trees.
The patches will be sent as a follow-on to this message to the
driver-devel list for people to see.
thanks,
greg k-h
--------------
drivers/staging/comedi/drivers/das08_cs.c | 1 -
drivers/staging/hv/netvsc_drv.c | 3 ++
drivers/staging/hv/ring_buffer.c | 3 +-
drivers/staging/hv/storvsc_api.h | 4 +-
drivers/staging/hv/storvsc_drv.c | 11 +++++---
drivers/staging/octeon/Kconfig | 2 +-
drivers/staging/rt2860/usb_main_dev.c | 41 +++++++++++++++++++++++++++-
drivers/staging/spectra/Kconfig | 1 +
drivers/staging/spectra/ffsport.c | 1 +
drivers/staging/wlan-ng/cfg80211.c | 3 ++
drivers/staging/zram/zram_drv.c | 1 +
11 files changed, 59 insertions(+), 12 deletions(-)
---------------
Andreas Bombe (1):
staging: comedi das08_cs.c: Fix io_req_t conversion
Ben Hutchings (1):
Staging: rt2870sta: Add more device IDs from vendor drivers
Geert Uytterhoeven (1):
staging: spectra needs <linux/slab.h>
Haiyang Zhang (2):
staging: hv: Fix missing functions for net_device_ops
staging: hv: Fixed the value of the 64bit-hole inside ring buffer
Hank Janssen (3):
staging: hv: Fixed bounce kmap problem by using correct index
staging: hv: Increased storvsc ringbuffer and max_io_requests
staging: hv: Fixed lockup problem with bounce_buffer scatter list
Jeff Mahoney (1):
Staging: spectra: depend on X86_MRST
Karl Relton (1):
Staging: wlan-ng: Explicitly set some fields in cfg80211 interface
Randy Dunlap (1):
Staging: octeon: depends on NETDEVICES
Shahar Havivi (1):
Staging: zram: free device memory when init fails
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/