6 files changed, 34 insertions, 17 deletions

diff --git a/Documentation/cpu-freq/core.txt b/Documentation/cpu-freq/core.txt
index 29b3f9ffc66c..ce0666e51036 100644
--- a/Documentation/cpu-freq/core.txt
+++ b/Documentation/cpu-freq/core.txt
@@ -24,7 +24,7 @@ Contents:
 1. General Information
 =======================
 
-The CPUFreq core code is located in linux/kernel/cpufreq.c. This
+The CPUFreq core code is located in drivers/cpufreq/cpufreq.c. This
 cpufreq code offers a standardized interface for the CPUFreq
 architecture drivers (those pieces of code that do actual
 frequency transitions), as well as to "notifiers". These are device
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index 46f2a559b27c..64ce44da5936 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -216,17 +216,6 @@ Who:	Thomas Gleixner <tglx@linutronix.de>
 
 ---------------------------
 
-What:   i2c-ite and i2c-algo-ite drivers
-When:   September 2006
-Why:    These drivers never compiled since they were added to the kernel
-        tree 5 years ago. This feature removal can be reevaluated if
-        someone shows interest in the drivers, fixes them and takes over
-        maintenance.
-        http://marc.theaimsgroup.com/?l=linux-mips&m=115040510817448
-Who:    Jean Delvare <khali@linux-fr.org>
-
----------------------------
-
 What:   Bridge netfilter deferred IPv4/IPv6 output hook calling
 When:   January 2007
 Why:    The deferred output hooks are a layering violation causing unusual
@@ -270,3 +259,25 @@ Why:	The new layer 3 independant connection tracking replaces the old
 Who:    Patrick McHardy <kaber@trash.net>
 
 ---------------------------
+
+What:   ACPI hooks (X86_SPEEDSTEP_CENTRINO_ACPI) in speedstep-centrino driver
+When:   December 2006
+Why:    Speedstep-centrino driver with ACPI hooks and acpi-cpufreq driver are
+        functionally very much similar. They talk to ACPI in same way. Only
+        difference between them is the way they do frequency transitions.
+        One uses MSRs and the other one uses IO ports. Functionaliy of
+        speedstep_centrino with ACPI hooks is now merged into acpi-cpufreq.
+        That means one common driver will support all Intel Enhanced Speedstep
+        capable CPUs. That means less confusion over name of
+        speedstep-centrino driver (with that driver supposed to be used on
+        non-centrino platforms). That means less duplication of code and
+        less maintenance effort and no possibility of these two drivers
+        going out of sync.
+        Current users of speedstep_centrino with ACPI hooks are requested to
+        switch over to acpi-cpufreq driver. speedstep-centrino will continue
+        to work using older non-ACPI static table based scheme even after this
+        date.
+
+Who:    Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
+
+---------------------------
diff --git a/Documentation/filesystems/ocfs2.txt b/Documentation/filesystems/ocfs2.txt
index af6defd10cb6..8ccf0c1b58ed 100644
--- a/Documentation/filesystems/ocfs2.txt
+++ b/Documentation/filesystems/ocfs2.txt
@@ -54,3 +54,6 @@ errors=panic		Panic and halt the machine if an error occurs.
 intr            (*)     Allow signals to interrupt cluster operations.
 nointr                  Do not allow signals to interrupt cluster
                         operations.
+atime_quantum=60(*)     OCFS2 will not update atime unless this number
+                        of seconds has passed since the last update.
+                        Set to zero to always update atime.
diff --git a/Documentation/i2c/busses/i2c-amd8111 b/Documentation/i2c/busses/i2c-amd8111
index db294ee7455a..460dd6635fd2 100644
--- a/Documentation/i2c/busses/i2c-amd8111
+++ b/Documentation/i2c/busses/i2c-amd8111
@@ -5,7 +5,7 @@ Supported adapters:
 
 Datasheets:
         AMD datasheet not yet available, but almost everything can be found
-        in publically available ACPI 2.0 specification, which the adapter 
+        in the publicly available ACPI 2.0 specification, which the adapter
         follows.
 
 Author: Vojtech Pavlik <vojtech@suse.cz>
diff --git a/Documentation/i2c/busses/i2c-i801 b/Documentation/i2c/busses/i2c-i801
index e46c23458242..3db69a086c41 100644
--- a/Documentation/i2c/busses/i2c-i801
+++ b/Documentation/i2c/busses/i2c-i801
@@ -9,7 +9,10 @@ Supported adapters:
   * Intel 82801EB/ER (ICH5) (HW PEC supported, 32 byte buffer not supported)
   * Intel 6300ESB
   * Intel 82801FB/FR/FW/FRW (ICH6)
-  * Intel ICH7
+  * Intel 82801G (ICH7)
+  * Intel 631xESB/632xESB (ESB2)
+  * Intel 82801H (ICH8)
+  * Intel ICH9
     Datasheets: Publicly available at the Intel website
 
 Authors: 
diff --git a/Documentation/i2c/busses/i2c-nforce2 b/Documentation/i2c/busses/i2c-nforce2
index cd49c428a3ab..7f61fbc03f7f 100644
--- a/Documentation/i2c/busses/i2c-nforce2
+++ b/Documentation/i2c/busses/i2c-nforce2
@@ -10,11 +10,11 @@ Supported adapters:
   * nForce4 MCP51              10de:0264
   * nForce4 MCP55              10de:0368
 
-Datasheet: not publically available, but seems to be similar to the
+Datasheet: not publicly available, but seems to be similar to the
            AMD-8111 SMBus 2.0 adapter.
 
 Authors:
-        Hans-Frieder Vogt <hfvogt@arcor.de>, 
+        Hans-Frieder Vogt <hfvogt@gmx.net>,
         Thomas Leibold <thomas@plx.com>, 
         Patrick Dreker <patrick@dreker.de>
         
@@ -38,7 +38,7 @@ Notes
 -----
 
 The SMBus adapter in the nForce2 chipset seems to be very similar to the
-SMBus 2.0 adapter in the AMD-8111 southbridge. However, I could only get
+SMBus 2.0 adapter in the AMD-8111 south bridge. However, I could only get
 the driver to work with direct I/O access, which is different to the EC
 interface of the AMD-8111. Tested on Asus A7N8X. The ACPI DSDT table of the
 Asus A7N8X lists two SMBuses, both of which are supported by this driver.