---

yaml --- r: 136517 b: refs/heads/master c: 7106a5a h: refs/heads/master i: 136515: 504766a v: v3
git-mirror · Jan 11, 2009 · 19a3d89 · 19a3d89
1 parent efee44c
commit 19a3d89
Show file tree

Hide file tree

Showing 2,069 changed files with 19,622 additions and 59,728 deletions.
diff --git a/[refs] b/[refs]
@@ -1,2 +1,2 @@
 ---
-refs/heads/master: 6a385db5ce7f1fd2c68ec511e44587b67dab8fca
+refs/heads/master: 7106a5ab89c50c6b5aadea0850b40323804a922d
diff --git a/trunk/CREDITS b/trunk/CREDITS
@@ -3786,11 +3786,14 @@ S: The Netherlands
 
 N: David Woodhouse
 E: dwmw2@infradead.org
-D: JFFS2 file system, Memory Technology Device subsystem,
+D: ARCnet stuff, Applicom board driver, SO_BINDTODEVICE,
+D: some Alpha platform porting from 2.0, Memory Technology Devices,
+D: Acquire watchdog timer, PC speaker driver maintenance,
 D: various other stuff that annoyed me by not working.
-S: c/o Intel Corporation
-S: Pipers Way
-S: Swindon. SN3 1RJ
+S: c/o Red Hat Engineering
+S: Rustat House
+S: 60 Clifton Road
+S: Cambridge. CB1 7EG
 S: England
 
 N: Chris Wright

diff --git a/trunk/Documentation/DMA-API.txt b/trunk/Documentation/DMA-API.txt
@@ -170,15 +170,16 @@ Returns: 0 if successful and a negative error if not.
 u64
 dma_get_required_mask(struct device *dev)
 
-This API returns the mask that the platform requires to
-operate efficiently.  Usually this means the returned mask
+After setting the mask with dma_set_mask(), this API returns the
+actual mask (within that already set) that the platform actually
+requires to operate efficiently.  Usually this means the returned mask
 is the minimum required to cover all of memory.  Examining the
 required mask gives drivers with variable descriptor sizes the
 opportunity to use smaller descriptors as necessary.
 
 Requesting the required mask does not alter the current mask.  If you
-wish to take advantage of it, you should issue a dma_set_mask()
-call to set the mask to the value returned.
+wish to take advantage of it, you should issue another dma_set_mask()
+call to lower the mask again.
 
 
 Part Id - Streaming DMA mappings

diff --git a/trunk/Documentation/accounting/getdelays.c b/trunk/Documentation/accounting/getdelays.c
@@ -392,10 +392,6 @@ int main(int argc, char *argv[])
 			goto err;
 		}
 	}
-	if (!maskset && !tid && !containerset) {
-		usage();
-		goto err;
-	}
 
 	do {
 		int i;

diff --git a/trunk/Documentation/cgroups/cgroups.txt b/trunk/Documentation/cgroups/cgroups.txt
@@ -1,8 +1,7 @@
 				CGROUPS
 				-------
 
-Written by Paul Menage <menage@google.com> based on
-Documentation/cgroups/cpusets.txt
+Written by Paul Menage <menage@google.com> based on Documentation/cpusets.txt
 
 Original copyright statements from cpusets.txt:
 Portions Copyright (C) 2004 BULL SA.
@@ -69,7 +68,7 @@ On their own, the only use for cgroups is for simple job
 tracking. The intention is that other subsystems hook into the generic
 cgroup support to provide new attributes for cgroups, such as
 accounting/limiting the resources which processes in a cgroup can
-access. For example, cpusets (see Documentation/cgroups/cpusets.txt) allows
+access. For example, cpusets (see Documentation/cpusets.txt) allows
 you to associate a set of CPUs and a set of memory nodes with the
 tasks in each cgroup.
 

diff --git a/trunk/Documentation/cgroups/cpuacct.txt → trunk/Documentation/controllers/cpuacct.txt b/trunk/Documentation/cgroups/cpuacct.txt → trunk/Documentation/controllers/cpuacct.txt
diff --git a/trunk/Documentation/cgroups/devices.txt → trunk/Documentation/controllers/devices.txt b/trunk/Documentation/cgroups/devices.txt → trunk/Documentation/controllers/devices.txt
diff --git a/trunk/Documentation/cgroups/memcg_test.txt → .../Documentation/controllers/memcg_test.txt b/trunk/Documentation/cgroups/memcg_test.txt → .../Documentation/controllers/memcg_test.txt
@@ -6,7 +6,7 @@ Because VM is getting complex (one of reasons is memcg...), memcg's behavior
 is complex. This is a document for memcg's internal behavior.
 Please note that implementation details can be changed.
 
-(*) Topics on API should be in Documentation/cgroups/memory.txt)
+(*) Topics on API should be in Documentation/controllers/memory.txt)
 
 0. How to record usage ?
    2 objects are used.

diff --git a/trunk/Documentation/cgroups/memory.txt → trunk/Documentation/controllers/memory.txt b/trunk/Documentation/cgroups/memory.txt → trunk/Documentation/controllers/memory.txt
diff --git a/...ocumentation/cgroups/resource_counter.txt → ...entation/controllers/resource_counter.txt b/...ocumentation/cgroups/resource_counter.txt → ...entation/controllers/resource_counter.txt
diff --git a/trunk/Documentation/cgroups/cpusets.txt → trunk/Documentation/cpusets.txt b/trunk/Documentation/cgroups/cpusets.txt → trunk/Documentation/cpusets.txt
diff --git a/trunk/Documentation/cputopology.txt b/trunk/Documentation/cputopology.txt
@@ -18,11 +18,11 @@ For an architecture to support this feature, it must define some of
 these macros in include/asm-XXX/topology.h:
 #define topology_physical_package_id(cpu)
 #define topology_core_id(cpu)
-#define topology_thread_cpumask(cpu)
-#define topology_core_cpumask(cpu)
+#define topology_thread_siblings(cpu)
+#define topology_core_siblings(cpu)
 
 The type of **_id is int.
-The type of siblings is (const) struct cpumask *.
+The type of siblings is cpumask_t.
 
 To be consistent on all architectures, include/linux/topology.h
 provides default definitions for any of the above macros that are

diff --git a/trunk/Documentation/filesystems/nfs-rdma.txt b/trunk/Documentation/filesystems/nfs-rdma.txt
@@ -251,7 +251,7 @@ NFS/RDMA Setup
 
     Instruct the server to listen on the RDMA transport:
 
-    $ echo rdma 20049 > /proc/fs/nfsd/portlist
+    $ echo rdma 2050 > /proc/fs/nfsd/portlist
 
   - On the client system
 
@@ -263,7 +263,7 @@ NFS/RDMA Setup
     Regardless of how the client was built (module or built-in), use this
     command to mount the NFS/RDMA server:
 
-    $ mount -o rdma,port=20049 <IPoIB-server-name-or-address>:/<export> /mnt
+    $ 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.