---

yaml
---
r: 140367
b: refs/heads/master
c: e3375ac
h: refs/heads/master
i:
  140365: be3f2d6
  140363: c39a208
  140359: 1a54e32
  140351: 87a1ce8
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 4e76c5ccd5ac9bd003467d3bb0f49b18572dd4cd
+refs/heads/master: e3375ac767b847127df57d186a26abf83d055982

trunk/CREDITS

@@ -495,11 +495,6 @@ S: Kopmansg 2
 S: 411 13  Goteborg
 S: Sweden
 
-N: Paul Bristow
-E: paul@paulbristow.net
-W: http://paulbristow.net/linux/idefloppy.html
-D: Maintainer of IDE/ATAPI floppy driver
-
 N: Dominik Brodowski
 E: linux@brodo.de
 W: http://www.brodo.de/
@@ -2647,10 +2642,6 @@ S: C/ Mieses 20, 9-B
 S: Valladolid 47009
 S: Spain
 
-N: Gadi Oxman
-E: gadio@netvision.net.il
-D: Original author and maintainer of IDE/ATAPI floppy/tape drivers
-
 N: Greg Page
 E: gpage@sovereign.org
 D: IPX development and support

trunk/Documentation/ABI/testing/sysfs-bus-pci

@@ -41,49 +41,6 @@ Description:
 		for the device and attempt to bind to it.  For example:
 		# echo "8086 10f5" > /sys/bus/pci/drivers/foo/new_id
 
-What:		/sys/bus/pci/drivers/.../remove_id
-Date:		February 2009
-Contact:	Chris Wright <chrisw@sous-sol.org>
-Description:
-		Writing a device ID to this file will remove an ID
-		that was dynamically added via the new_id sysfs entry.
-		The format for the device ID is:
-		VVVV DDDD SVVV SDDD CCCC MMMM.	That is Vendor ID, Device
-		ID, Subsystem Vendor ID, Subsystem Device ID, Class,
-		and Class Mask.  The Vendor ID and Device ID fields are
-		required, the rest are optional.  After successfully
-		removing an ID, the driver will no longer support the
-		device.  This is useful to ensure auto probing won't
-		match the driver to the device.  For example:
-		# echo "8086 10f5" > /sys/bus/pci/drivers/foo/remove_id
-
-What:		/sys/bus/pci/rescan
-Date:		January 2009
-Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
-Description:
-		Writing a non-zero value to this attribute will
-		force a rescan of all PCI buses in the system, and
-		re-discover previously removed devices.
-		Depends on CONFIG_HOTPLUG.
-
-What:		/sys/bus/pci/devices/.../remove
-Date:		January 2009
-Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
-Description:
-		Writing a non-zero value to this attribute will
-		hot-remove the PCI device and any of its children.
-		Depends on CONFIG_HOTPLUG.
-
-What:		/sys/bus/pci/devices/.../rescan
-Date:		January 2009
-Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
-Description:
-		Writing a non-zero value to this attribute will
-		force a rescan of the device's parent bus and all
-		child buses, and re-discover devices removed earlier
-		from this part of the device tree.
-		Depends on CONFIG_HOTPLUG.
-
 What:		/sys/bus/pci/devices/.../vpd
 Date:		February 2008
 Contact:	Ben Hutchings <bhutchings@solarflare.com>
@@ -95,30 +52,3 @@ Description:
 		that some devices may have malformatted data.  If the
 		underlying VPD has a writable section then the
 		corresponding section of this file will be writable.
-
-What:		/sys/bus/pci/devices/.../virtfnN
-Date:		March 2009
-Contact:	Yu Zhao <yu.zhao@intel.com>
-Description:
-		This symbolic link appears when hardware supports the SR-IOV
-		capability and the Physical Function driver has enabled it.
-		The symbolic link points to the PCI device sysfs entry of the
-		Virtual Function whose index is N (0...MaxVFs-1).
-
-What:		/sys/bus/pci/devices/.../dep_link
-Date:		March 2009
-Contact:	Yu Zhao <yu.zhao@intel.com>
-Description:
-		This symbolic link appears when hardware supports the SR-IOV
-		capability and the Physical Function driver has enabled it,
-		and this device has vendor specific dependencies with others.
-		The symbolic link points to the PCI device sysfs entry of
-		Physical Function this device depends on.
-
-What:		/sys/bus/pci/devices/.../physfn
-Date:		March 2009
-Contact:	Yu Zhao <yu.zhao@intel.com>
-Description:
-		This symbolic link appears when a device is a Virtual Function.
-		The symbolic link points to the PCI device sysfs entry of the
-		Physical Function this device associates with.

trunk/Documentation/ABI/testing/sysfs-class-regulator

@@ -4,8 +4,8 @@ KernelVersion:	2.6.26
 Contact:	Liam Girdwood <lrg@slimlogic.co.uk>
 Description:
 		Some regulator directories will contain a field called
-		state. This reports the regulator enable control, for
-		regulators which can report that input value.
+		state. This reports the regulator enable status, for
+		regulators which can report that value.
 
 		This will be one of the following strings:
 
@@ -14,54 +14,16 @@ Description:
 		'unknown'
 
 		'enabled' means the regulator output is ON and is supplying
-		power to the system (assuming no error prevents it).
+		power to the system.
 
 		'disabled' means the regulator output is OFF and is not
-		supplying power to the system (unless some non-Linux
-		control has enabled it).
+		supplying power to the system..
 
 		'unknown' means software cannot determine the state, or
 		the reported state is invalid.
 
 		NOTE: this field can be used in conjunction with microvolts
-		or microamps to determine configured regulator output levels.
-
-
-What:		/sys/class/regulator/.../status
-Description:
-		Some regulator directories will contain a field called
-		"status". This reports the current regulator status, for
-		regulators which can report that output value.
-
-		This will be one of the following strings:
-
-			off
-			on
-			error
-			fast
-			normal
-			idle
-			standby
-
-		"off" means the regulator is not supplying power to the
-		system.
-
-		"on" means the regulator is supplying power to the system,
-		and the regulator can't report a detailed operation mode.
-
-		"error" indicates an out-of-regulation status such as being
-		disabled due to thermal shutdown, or voltage being unstable
-		because of problems with the input power supply.
-
-		"fast", "normal", "idle", and "standby" are all detailed
-		regulator operation modes (described elsewhere).  They
-		imply "on", but provide more detail.
-
-		Note that regulator status is a function of many inputs,
-		not limited to control inputs from Linux.  For example,
-		the actual load presented may trigger "error" status; or
-		a regulator may be enabled by another user, even though
-		Linux did not enable it.
+		and microamps to determine regulator output levels.
 
 
 What:		/sys/class/regulator/.../type
@@ -96,7 +58,7 @@ Description:
 		Some regulator directories will contain a field called
 		microvolts. This holds the regulator output voltage setting
 		measured in microvolts (i.e. E-6 Volts), for regulators
-		which can report the control input for voltage.
+		which can report that voltage.
 
 		NOTE: This value should not be used to determine the regulator
 		output voltage level as this value is the same regardless of
@@ -111,7 +73,7 @@ Description:
 		Some regulator directories will contain a field called
 		microamps. This holds the regulator output current limit
 		setting measured in microamps (i.e. E-6 Amps), for regulators
-		which can report the control input for a current limit.
+		which can report that current.
 
 		NOTE: This value should not be used to determine the regulator
 		output current level as this value is the same regardless of
@@ -125,7 +87,7 @@ Contact:	Liam Girdwood <lrg@slimlogic.co.uk>
 Description:
 		Some regulator directories will contain a field called
 		opmode. This holds the current regulator operating mode,
-		for regulators which can report that control input value.
+		for regulators which can report it.
 
 		The opmode value can be one of the following strings:
 
@@ -139,8 +101,7 @@ Description:
 
 		NOTE: This value should not be used to determine the regulator
 		output operating mode as this value is the same regardless of
-		whether the regulator is enabled or disabled.  A "status"
-		attribute may be available to determine the actual mode.
+		whether the regulator is enabled or disabled.
 
 
 What:		/sys/class/regulator/.../min_microvolts