---

yaml
---
r: 178772
b: refs/heads/master
c: c7c17c2
h: refs/heads/master
v: v3

[refs]

@@ -1,2 +1,2 @@
 ---
-refs/heads/master: db677ffa5f5a4f15b9dad4d132b3477b80766d82
+refs/heads/master: c7c17c2779075e675cb3c7fe2ecde67e226771fb

trunk/.gitignore

@@ -22,7 +22,6 @@
 *.lst
 *.symtypes
 *.order
-modules.builtin
 *.elf
 *.bin
 *.gz
@@ -46,8 +45,14 @@ Module.symvers
 #
 # Generated include files
 #
+include/asm
+include/asm-*/asm-offsets.h
 include/config
+include/linux/autoconf.h
+include/linux/compile.h
 include/linux/version.h
+include/linux/utsrelease.h
+include/linux/bounds.h
 include/generated
 
 # stgit generated dirs

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

@@ -21,27 +21,25 @@ Contact:	Alan Stern <stern@rowland.harvard.edu>
 Description:
 		Each USB device directory will contain a file named
 		power/level.  This file holds a power-level setting for
-		the device, either "on" or "auto".
+		the device, one of "on", "auto", or "suspend".
 
 		"on" means that the device is not allowed to autosuspend,
 		although normal suspends for system sleep will still
 		be honored.  "auto" means the device will autosuspend
 		and autoresume in the usual manner, according to the
-		capabilities of its driver.
+		capabilities of its driver.  "suspend" means the device
+		is forced into a suspended state and it will not autoresume
+		in response to I/O requests.  However remote-wakeup requests
+		from the device may still be enabled (the remote-wakeup
+		setting is controlled separately by the power/wakeup
+		attribute).
 
 		During normal use, devices should be left in the "auto"
-		level.  The "on" level is meant for administrative uses.
+		level.  The other levels are meant for administrative uses.
 		If you want to suspend a device immediately but leave it
 		free to wake up in response to I/O requests, you should
 		write "0" to power/autosuspend.
 
-		Device not capable of proper suspend and resume should be
-		left in the "on" level.  Although the USB spec requires
-		devices to support suspend/resume, many of them do not.
-		In fact so many don't that by default, the USB core
-		initializes all non-hub devices in the "on" level.  Some
-		drivers may change this setting when they are bound.
-
 What:		/sys/bus/usb/devices/.../power/persist
 Date:		May 2007
 KernelVersion:	2.6.23
@@ -146,16 +144,3 @@ Description:
 
 		Write a 1 to force the device to disconnect
 		(equivalent to unplugging a wired USB device).
-
-What:		/sys/bus/usb/drivers/.../remove_id
-Date:		November 2009
-Contact:	CHENG Renquan <rqcheng@smu.edu.sg>
-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:
-		idVendor idProduct.	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 "046d c315" > /sys/bus/usb/drivers/foo/remove_id

trunk/Documentation/ABI/testing/sysfs-class-uwb_rc-wusbhc

@@ -23,16 +23,3 @@ Description:
                 Since this relates to security (specifically, the
                 lifetime of PTKs and GTKs) it should not be changed
                 from the default.
-
-What:           /sys/class/uwb_rc/uwbN/wusbhc/wusb_phy_rate
-Date:           August 2009
-KernelVersion:  2.6.32
-Contact:        David Vrabel <david.vrabel@csr.com>
-Description:
-                The maximum PHY rate to use for all connected devices.
-                This is only of limited use for testing and
-                development as the hardware's automatic rate
-                adaptation is better then this simple control.
-
-                Refer to [ECMA-368] section 10.3.1.1 for the value to
-                use.

trunk/Documentation/ABI/testing/sysfs-devices-memory

@@ -60,19 +60,6 @@ Description:
 Users:		hotplug memory remove tools
 		https://w3.opensource.ibm.com/projects/powerpc-utils/
 
-
-What:		/sys/devices/system/memoryX/nodeY
-Date:		October 2009
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		When CONFIG_NUMA is enabled, a symbolic link that
-		points to the corresponding NUMA node directory.
-
-		For example, the following symbolic link is created for
-		memory section 9 on node0:
-		/sys/devices/system/memory/memory9/node0 -> ../../node/node0
-
-
 What:		/sys/devices/system/node/nodeX/memoryY
 Date:		September 2008
 Contact:	Gary Hade <garyhade@us.ibm.com>
@@ -83,3 +70,4 @@ Description:
 		memory section directory.  For example, the following symbolic
 		link is created for memory section 9 on node0.
 		/sys/devices/system/node/node0/memory9 -> ../../memory/memory9
+

trunk/Documentation/ABI/testing/sysfs-devices-system-cpu

@@ -62,35 +62,6 @@ Description:	CPU topology files that describe kernel limits related to
 		See Documentation/cputopology.txt for more information.
 
 
-What:		/sys/devices/system/cpu/probe
-		/sys/devices/system/cpu/release
-Date:		November 2009
-Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
-Description:	Dynamic addition and removal of CPU's.  This is not hotplug
-		removal, this is meant complete removal/addition of the CPU
-		from the system.
-
-		probe: writes to this file will dynamically add a CPU to the
-		system.  Information written to the file to add CPU's is
-		architecture specific.
-
-		release: writes to this file dynamically remove a CPU from
-		the system.  Information writtento the file to remove CPU's
-		is architecture specific.
-
-What:		/sys/devices/system/cpu/cpu#/node
-Date:		October 2009
-Contact:	Linux memory management mailing list <linux-mm@kvack.org>
-Description:	Discover NUMA node a CPU belongs to
-
-		When CONFIG_NUMA is enabled, a symbolic link that points
-		to the corresponding NUMA node directory.
-
-		For example, the following symlink is created for cpu42
-		in NUMA node 2:
-
-		/sys/devices/system/cpu/cpu42/node2 -> ../../node/node2
-
 
 What:		/sys/devices/system/cpu/cpu#/node
 Date:		October 2009
@@ -165,24 +136,6 @@ Description:	Discover cpuidle policy and mechanism
 		See files in Documentation/cpuidle/ for more information.
 
 
-What:		/sys/devices/system/cpu/cpu#/cpufreq/*
-Date:		pre-git history
-Contact:	cpufreq@vger.kernel.org
-Description:	Discover and change clock speed of CPUs
-
-		Clock scaling allows you to change the clock speed of the
-		CPUs on the fly. This is a nice method to save battery
-		power, because the lower the clock speed, the less power
-		the CPU consumes.
-
-		There are many knobs to tweak in this directory.
-
-		See files in Documentation/cpu-freq/ for more information.
-
-		In particular, read Documentation/cpu-freq/user-guide.txt
-		to learn how to control the knobs.
-
-
 What:      /sys/devices/system/cpu/cpu*/cache/index*/cache_disable_X
 Date:      August 2008
 KernelVersion:	2.6.27