Merge branch 'for-upstream/acpi-test' of... (8294fafd) · Commits · e / devices / android_kernel_teracube_2e

Documentation/feature-removal-schedule.txt

+22 −0

Original line number	Diff line number	Diff line
		@@ -308,9 +308,31 @@ Who: Matthew Wilcox <willy@linux.intel.com>

		---------------------------

		What: SCTP_GET_PEER_ADDRS_NUM_OLD, SCTP_GET_PEER_ADDRS_OLD,
		SCTP_GET_LOCAL_ADDRS_NUM_OLD, SCTP_GET_LOCAL_ADDRS_OLD
		When: June 2009
		Why: A newer version of the options have been introduced in 2005 that
		removes the limitions of the old API. The sctp library has been
		converted to use these new options at the same time. Any user
		space app that directly uses the old options should convert to using
		the new options.
		Who: Vlad Yasevich <vladislav.yasevich@hp.com>

		---------------------------

		What: CONFIG_THERMAL_HWMON
		When: January 2009
		Why: This option was introduced just to allow older lm-sensors userspace
		to keep working over the upgrade to 2.6.26. At the scheduled time of
		removal fixed lm-sensors (2.x or 3.x) should be readily available.
		Who: Rene Herman <rene.herman@gmail.com>

		---------------------------

		What: Code that is now under CONFIG_WIRELESS_EXT_SYSFS
		(in net/core/net-sysfs.c)
		When: After the only user (hal) has seen a release with the patches
		for enough time, probably some time in 2010.
		Why: Over 1K .text/.data size reduction, data is available in other
		ways (ioctls)
		Who: Johannes Berg <johannes@sipsolutions.net>

Documentation/filesystems/configfs/configfs.txt

+4 −6

Original line number	Diff line number	Diff line
		@@ -233,12 +233,10 @@ accomplished via the group operations specified on the group's
		config_item_type.

		struct configfs_group_operations {
		int (make_item)(struct config_group group,
		const char *name,
		struct config_item **new_item);
		int (make_group)(struct config_group group,
		const char *name,
		struct config_group **new_group);
		struct config_item (make_item)(struct config_group *group,
		const char *name);
		struct config_group (make_group)(struct config_group *group,
		const char *name);
		int (commit_item)(struct config_item item);
		void (disconnect_notify)(struct config_group group,
		struct config_item *item);

Documentation/filesystems/configfs/configfs_example.c

+6 −8

Original line number	Diff line number	Diff line
		@@ -273,13 +273,13 @@ static inline struct simple_children to_simple_children(struct config_item ite
		return item ? container_of(to_config_group(item), struct simple_children, group) : NULL;
		}

		static int simple_children_make_item(struct config_group group, const char name, struct config_item **new_item)
		static struct config_item simple_children_make_item(struct config_group group, const char *name)
		{
		struct simple_child *simple_child;

		simple_child = kzalloc(sizeof(struct simple_child), GFP_KERNEL);
		if (!simple_child)
		return -ENOMEM;
		return ERR_PTR(-ENOMEM);


		config_item_init_type_name(&simple_child->item, name,
		@@ -287,8 +287,7 @@ static int simple_children_make_item(struct config_group group, const char nam

		simple_child->storeme = 0;

		*new_item = &simple_child->item;
		return 0;
		return &simple_child->item;
		}

		static struct configfs_attribute simple_children_attr_description = {
		@@ -360,21 +359,20 @@ static struct configfs_subsystem simple_children_subsys = {
		* children of its own.
		*/

		static int group_children_make_group(struct config_group group, const char name, struct config_group **new_group)
		static struct config_group group_children_make_group(struct config_group group, const char *name)
		{
		struct simple_children *simple_children;

		simple_children = kzalloc(sizeof(struct simple_children),
		GFP_KERNEL);
		if (!simple_children)
		return -ENOMEM;
		return ERR_PTR(-ENOMEM);


		config_group_init_type_name(&simple_children->group, name,
		&simple_children_type);

		*new_group = &simple_children->group;
		return 0;
		return &simple_children->group;
		}

		static struct configfs_attribute group_children_attr_description = {

Documentation/filesystems/nfs-rdma.txt

+59 −44

Original line number	Diff line number	Diff line
		@@ -5,7 +5,7 @@
		################################################################################

		Author: NetApp and Open Grid Computing
		Date: April 15, 2008
		Date: May 29, 2008

		Table of Contents
		~~~~~~~~~~~~~~~~~
		@@ -60,16 +60,18 @@ Installation
		The procedures described in this document have been tested with
		distributions from Red Hat's Fedora Project (http://fedora.redhat.com/).

		- Install nfs-utils-1.1.1 or greater on the client
		- Install nfs-utils-1.1.2 or greater on the client

		An NFS/RDMA mount point can only be obtained by using the mount.nfs
		command in nfs-utils-1.1.1 or greater. To see which version of mount.nfs
		you are using, type:
		An NFS/RDMA mount point can be obtained by using the mount.nfs command in
		nfs-utils-1.1.2 or greater (nfs-utils-1.1.1 was the first nfs-utils
		version with support for NFS/RDMA mounts, but for various reasons we
		recommend using nfs-utils-1.1.2 or greater). To see which version of
		mount.nfs you are using, type:

		> /sbin/mount.nfs -V
		$ /sbin/mount.nfs -V

		If the version is less than 1.1.1 or the command does not exist,
		then you will need to install the latest version of nfs-utils.
		If the version is less than 1.1.2 or the command does not exist,
		you should install the latest version of nfs-utils.

		Download the latest package from:

		@@ -77,22 +79,33 @@ Installation

		Uncompress the package and follow the installation instructions.

		If you will not be using GSS and NFSv4, the installation process
		can be simplified by disabling these features when running configure:
		If you will not need the idmapper and gssd executables (you do not need
		these to create an NFS/RDMA enabled mount command), the installation
		process can be simplified by disabling these features when running
		configure:

		> ./configure --disable-gss --disable-nfsv4
		$ ./configure --disable-gss --disable-nfsv4

		For more information on this see the package's README and INSTALL files.
		To build nfs-utils you will need the tcp_wrappers package installed. For
		more information on this see the package's README and INSTALL files.

		After building the nfs-utils package, there will be a mount.nfs binary in
		the utils/mount directory. This binary can be used to initiate NFS v2, v3,
		or v4 mounts. To initiate a v4 mount, the binary must be called mount.nfs4.
		The standard technique is to create a symlink called mount.nfs4 to mount.nfs.
		or v4 mounts. To initiate a v4 mount, the binary must be called
		mount.nfs4. The standard technique is to create a symlink called
		mount.nfs4 to mount.nfs.

		NOTE: mount.nfs and therefore nfs-utils-1.1.1 or greater is only needed
		This mount.nfs binary should be installed at /sbin/mount.nfs as follows:

		$ sudo cp utils/mount/mount.nfs /sbin/mount.nfs

		In this location, mount.nfs will be invoked automatically for NFS mounts
		by the system mount commmand.

		NOTE: mount.nfs and therefore nfs-utils-1.1.2 or greater is only needed
		on the NFS client machine. You do not need this specific version of
		nfs-utils on the server. Furthermore, only the mount.nfs command from
		nfs-utils-1.1.1 is needed on the client.
		nfs-utils-1.1.2 is needed on the client.

		- Install a Linux kernel with NFS/RDMA

		@@ -156,8 +169,8 @@ Check RDMA and NFS Setup
		this time. For example, if you are using a Mellanox Tavor/Sinai/Arbel
		card:

		> modprobe ib_mthca
		> modprobe ib_ipoib
		$ modprobe ib_mthca
		$ modprobe ib_ipoib

		If you are using InfiniBand, make sure there is a Subnet Manager (SM)
		running on the network. If your IB switch has an embedded SM, you can
		@@ -166,7 +179,7 @@ Check RDMA and NFS Setup

		If an SM is running on your network, you should see the following:

		> cat /sys/class/infiniband/driverX/ports/1/state
		$ cat /sys/class/infiniband/driverX/ports/1/state
		4: ACTIVE

		where driverX is mthca0, ipath5, ehca3, etc.
		@@ -174,10 +187,10 @@ Check RDMA and NFS Setup
		To further test the InfiniBand software stack, use IPoIB (this
		assumes you have two IB hosts named host1 and host2):

		host1> ifconfig ib0 a.b.c.x
		host2> ifconfig ib0 a.b.c.y
		host1> ping a.b.c.y
		host2> ping a.b.c.x
		host1$ ifconfig ib0 a.b.c.x
		host2$ ifconfig ib0 a.b.c.y
		host1$ ping a.b.c.y
		host2$ ping a.b.c.x

		For other device types, follow the appropriate procedures.

		@@ -202,11 +215,11 @@ NFS/RDMA Setup
		/vol0 192.168.0.47(fsid=0,rw,async,insecure,no_root_squash)
		/vol0 192.168.0.0/255.255.255.0(fsid=0,rw,async,insecure,no_root_squash)

		The IP address(es) is(are) the client's IPoIB address for an InfiniBand HCA or the
		cleint's iWARP address(es) for an RNIC.
		The IP address(es) is(are) the client's IPoIB address for an InfiniBand
		HCA or the cleint's iWARP address(es) for an RNIC.

		NOTE: The "insecure" option must be used because the NFS/RDMA client does not
		use a reserved port.
		NOTE: The "insecure" option must be used because the NFS/RDMA client does
		not use a reserved port.

		Each time a machine boots:

		@@ -214,43 +227,45 @@ NFS/RDMA Setup

		For InfiniBand using a Mellanox adapter:

		> modprobe ib_mthca
		> modprobe ib_ipoib
		> ifconfig ib0 a.b.c.d
		$ modprobe ib_mthca
		$ modprobe ib_ipoib
		$ ifconfig ib0 a.b.c.d

		NOTE: use unique addresses for the client and server

		- Start the NFS server

		If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config),
		load the RDMA transport module:
		If the NFS/RDMA server was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
		kernel config), load the RDMA transport module:

		> modprobe svcrdma
		$ modprobe svcrdma

		Regardless of how the server was built (module or built-in), start the server:
		Regardless of how the server was built (module or built-in), start the
		server:

		> /etc/init.d/nfs start
		$ /etc/init.d/nfs start

		or

		> service nfs start
		$ service nfs start

		Instruct the server to listen on the RDMA transport:

		> echo rdma 2050 > /proc/fs/nfsd/portlist
		$ echo rdma 2050 > /proc/fs/nfsd/portlist

		- On the client system

		If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in kernel config),
		load the RDMA client module:
		If the NFS/RDMA client was built as a module (CONFIG_SUNRPC_XPRT_RDMA=m in
		kernel config), load the RDMA client module:

		> modprobe xprtrdma.ko
		$ modprobe xprtrdma.ko

		Regardless of how the client was built (module or built-in), issue the mount.nfs command:
		Regardless of how the client was built (module or built-in), use this
		command to mount the NFS/RDMA server:

		> /path/to/your/mount.nfs <IPoIB-server-name-or-address>:/<export> /mnt -i -o rdma,port=2050
		$ mount -o rdma,port=2050 <IPoIB-server-name-or-address>:/<export> /mnt

		To verify that the mount is using RDMA, run "cat /proc/mounts" and check the
		"proto" field for the given mount.
		To verify that the mount is using RDMA, run "cat /proc/mounts" and check
		the "proto" field for the given mount.

		Congratulations! You're using NFS/RDMA!

Documentation/laptops/thinkpad-acpi.txt

+18 −8

Original line number	Diff line number	Diff line
		ThinkPad ACPI Extras Driver

		Version 0.20
		April 09th, 2008
		Version 0.21
		May 29th, 2008

		Borislav Deianov <borislav@users.sf.net>
		Henrique de Moraes Holschuh <hmh@hmh.eng.br>
		@@ -621,7 +621,8 @@ Bluetooth
		---------

		procfs: /proc/acpi/ibm/bluetooth
		sysfs device attribute: bluetooth_enable
		sysfs device attribute: bluetooth_enable (deprecated)
		sysfs rfkill class: switch "tpacpi_bluetooth_sw"

		This feature shows the presence and current state of a ThinkPad
		Bluetooth device in the internal ThinkPad CDC slot.
		@@ -643,8 +644,12 @@ Sysfs notes:
		0: disables Bluetooth / Bluetooth is disabled
		1: enables Bluetooth / Bluetooth is enabled.

		Note: this interface will be probably be superseded by the
		generic rfkill class, so it is NOT to be considered stable yet.
		Note: this interface has been superseded by the generic rfkill
		class. It has been deprecated, and it will be removed in year
		2010.

		rfkill controller switch "tpacpi_bluetooth_sw": refer to
		Documentation/rfkill.txt for details.

		Video output control -- /proc/acpi/ibm/video
		--------------------------------------------
		@@ -1374,7 +1379,8 @@ EXPERIMENTAL: WAN
		-----------------

		procfs: /proc/acpi/ibm/wan
		sysfs device attribute: wwan_enable
		sysfs device attribute: wwan_enable (deprecated)
		sysfs rfkill class: switch "tpacpi_wwan_sw"

		This feature is marked EXPERIMENTAL because the implementation
		directly accesses hardware registers and may not work as expected. USE
		@@ -1404,8 +1410,12 @@ Sysfs notes:
		0: disables WWAN card / WWAN card is disabled
		1: enables WWAN card / WWAN card is enabled.

		Note: this interface will be probably be superseded by the
		generic rfkill class, so it is NOT to be considered stable yet.
		Note: this interface has been superseded by the generic rfkill
		class. It has been deprecated, and it will be removed in year
		2010.

		rfkill controller switch "tpacpi_wwan_sw": refer to
		Documentation/rfkill.txt for details.

		Multiple Commands, Module Parameters
		------------------------------------