---

yaml --- r: 283142 b: refs/heads/master c: 8c93940 h: refs/heads/master v: v3
git-mirror · Jan 10, 2012 · 122ad5a · 122ad5a
1 parent 323f5d0
commit 122ad5a
Show file tree

Hide file tree

Showing 2,632 changed files with 71,849 additions and 124,172 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 28190145543260c155216b9bd3adf57bee50f8b2
+refs/heads/master: 8c939402e43b21ea8ac031b7f751fa0c6b0faf00
diff --git a/trunk/Documentation/ABI/stable/sysfs-bus-xen-backend b/trunk/Documentation/ABI/stable/sysfs-bus-xen-backend
diff --git a/trunk/Documentation/ABI/stable/sysfs-devices-system-xen_memory b/trunk/Documentation/ABI/stable/sysfs-devices-system-xen_memory
diff --git a/trunk/Documentation/ABI/testing/sysfs-bus-pci b/trunk/Documentation/ABI/testing/sysfs-bus-pci
@@ -66,24 +66,6 @@ Description:
 		re-discover previously removed devices.
 		Depends on CONFIG_HOTPLUG.
 
-What:		/sys/bus/pci/devices/.../msi_irqs/
-Date:		September, 2011
-Contact:	Neil Horman <nhorman@tuxdriver.com>
-Description:
-		The /sys/devices/.../msi_irqs directory contains a variable set
-		of sub-directories, with each sub-directory being named after a
-		corresponding msi irq vector allocated to that device.  Each
-		numbered sub-directory N contains attributes of that irq.
-		Note that this directory is not created for device drivers which
-		do not support msi irqs
-
-What:		/sys/bus/pci/devices/.../msi_irqs/<N>/mode
-Date:		September 2011
-Contact:	Neil Horman <nhorman@tuxdriver.com>
-Description:
-		This attribute indicates the mode that the irq vector named by
-		the parent directory is in (msi vs. msix)
-
 What:		/sys/bus/pci/devices/.../remove
 Date:		January 2009
 Contact:	Linux PCI developers <linux-pci@vger.kernel.org>

diff --git a/trunk/Documentation/ABI/testing/sysfs-bus-usb b/trunk/Documentation/ABI/testing/sysfs-bus-usb
@@ -119,31 +119,6 @@ Description:
 		Write a 1 to force the device to disconnect
 		(equivalent to unplugging a wired USB device).
 
-What:		/sys/bus/usb/drivers/.../new_id
-Date:		October 2011
-Contact:	linux-usb@vger.kernel.org
-Description:
-		Writing a device ID to this file will attempt to
-		dynamically add a new device ID to a USB device driver.
-		This may allow the driver to support more hardware than
-		was included in the driver's static device ID support
-		table at compile time. The format for the device ID is:
-		idVendor idProduct bInterfaceClass.
-		The vendor ID and device ID fields are required, the
-		interface class is optional.
-		Upon successfully adding an ID, the driver will probe
-		for the device and attempt to bind to it.  For example:
-		# echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
-
-What:		/sys/bus/usb-serial/drivers/.../new_id
-Date:		October 2011
-Contact:	linux-usb@vger.kernel.org
-Description:
-		For serial USB drivers, this attribute appears under the
-		extra bus folder "usb-serial" in sysfs; apart from that
-		difference, all descriptions from the entry
-		"/sys/bus/usb/drivers/.../new_id" apply.
-
 What:		/sys/bus/usb/drivers/.../remove_id
 Date:		November 2009
 Contact:	CHENG Renquan <rqcheng@smu.edu.sg>

diff --git a/trunk/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration b/trunk/Documentation/ABI/testing/sysfs-class-rtc-rtc0-device-rtc_calibration
diff --git a/trunk/Documentation/ABI/testing/sysfs-devices-platform-docg3 b/trunk/Documentation/ABI/testing/sysfs-devices-platform-docg3
diff --git a/trunk/Documentation/ABI/testing/sysfs-driver-hid-multitouch b/trunk/Documentation/ABI/testing/sysfs-driver-hid-multitouch