Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6 (e758936e) · Commits · e / devices / android_kernel_teracube_emerald

.mailmap

+2 −0

Original line number	Diff line number	Diff line
		@@ -96,4 +96,6 @@ Tejun Heo <htejun@gmail.com>
		Thomas Graf <tgraf@suug.ch>
		Tony Luck <tony.luck@intel.com>
		Tsuneo Yoshioka <Tsuneo.Yoshioka@f-secure.com>
		Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>
		Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
		Valdis Kletnieks <Valdis.Kletnieks@vt.edu>

+0 −2

Original line number	Diff line number	Diff line
		@@ -251,8 +251,6 @@ mono.txt
		- how to execute Mono-based .NET binaries with the help of BINFMT_MISC.
		moxa-smartio
		- file with info on installing/using Moxa multiport serial driver.
		mtrr.txt
		- how to use PPro Memory Type Range Registers to increase performance.
		mutex-design.txt
		- info on the generic mutex subsystem.
		namespaces/

0 → 100644

+27 −0

Original line number	Diff line number	Diff line
		What: /sys/firmware/sgi_uv/
		Date: August 2008
		Contact: Russ Anderson <rja@sgi.com>
		Description:
		The /sys/firmware/sgi_uv directory contains information
		about the SGI UV platform.

		Under that directory are a number of files:

		partition_id
		coherence_id

		The partition_id entry contains the partition id.
		SGI UV systems can be partitioned into multiple physical
		machines, which each partition running a unique copy
		of the operating system. Each partition will have a unique
		partition id. To display the partition id, use the command:

		cat /sys/firmware/sgi_uv/partition_id

		The coherence_id entry contains the coherence id.
		A partitioned SGI UV system can have one or more coherence
		domain. The coherence id indicates which coherence domain
		this partition is in. To display the coherence id, use the
		command:

		cat /sys/firmware/sgi_uv/coherence_id

0 → 100644

+26 −0

Original line number	Diff line number	Diff line
		What: /sys/class/gpio/
		Date: July 2008
		KernelVersion: 2.6.27
		Contact: David Brownell <dbrownell@users.sourceforge.net>
		Description:

		As a Kconfig option, individual GPIO signals may be accessed from
		userspace. GPIOs are only made available to userspace by an explicit
		"export" operation. If a given GPIO is not claimed for use by
		kernel code, it may be exported by userspace (and unexported later).
		Kernel code may export it for complete or partial access.

		GPIOs are identified as they are inside the kernel, using integers in
		the range 0..INT_MAX. See Documentation/gpio.txt for more information.

		/sys/class/gpio
		/export ... asks the kernel to export a GPIO to userspace
		/unexport ... to return a GPIO to the kernel
		/gpioN ... for each exported GPIO #N
		/value ... always readable, writes fail for input GPIOs
		/direction ... r/w as: in, out (default low); write: high, low
		/gpiochipN ... for each gpiochip; #N is its first GPIO
		/base ... (r/o) same as N
		/label ... (r/o) descriptive, not necessarily unique
		/ngpio ... (r/o) number of GPIOs; numbered N to N + (ngpio - 1)

+1 −1

Original line number	Diff line number	Diff line
		@@ -337,7 +337,7 @@ With scatterlists, you use the resulting mapping like this:
		int i, count = dma_map_sg(dev, sglist, nents, direction);
		struct scatterlist *sg;

		for (i = 0, sg = sglist; i < count; i++, sg++) {
		for_each_sg(sglist, sg, count, i) {
		hw_address[i] = sg_dma_address(sg);
		hw_len[i] = sg_dma_len(sg);
		}