14 files changed, 202 insertions, 134 deletions

diff --git a/Documentation/ABI/testing/sysfs-class-scsi_host b/Documentation/ABI/testing/sysfs-class-scsi_host
new file mode 100644
index 000000000000..29a4f892e433
--- /dev/null
+++ b/Documentation/ABI/testing/sysfs-class-scsi_host
@@ -0,0 +1,13 @@
+What:           /sys/class/scsi_host/hostX/isci_id
+Date:           June 2011
+Contact:        Dave Jiang <dave.jiang@intel.com>
+Description:
+                This file contains the enumerated host ID for the Intel
+                SCU controller. The Intel(R) C600 Series Chipset SATA/SAS
+                Storage Control Unit embeds up to two 4-port controllers in
+                a single PCI device.  The controllers are enumerated in order
+                which usually means the lowest number scsi_host corresponds
+                with the first controller, but this association is not
+                guaranteed.  The 'isci_id' attribute unambiguously identifies
+                the controller index: '0' for the first controller,
+                '1' for the second.
diff --git a/Documentation/DocBook/media/v4l/controls.xml b/Documentation/DocBook/media/v4l/controls.xml
index 85164016ed26..23fdf79f8cf3 100644
--- a/Documentation/DocBook/media/v4l/controls.xml
+++ b/Documentation/DocBook/media/v4l/controls.xml
@@ -1455,7 +1455,7 @@ Applicable to the H264 encoder.</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-h264-vui-sar-idc">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_H264_VUI_SAR_IDC</constant>&nbsp;</entry>
                 <entry>enum&nbsp;v4l2_mpeg_video_h264_vui_sar_idc</entry>
               </row>
@@ -1561,7 +1561,7 @@ Applicable to the H264 encoder.</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-h264-level">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_H264_LEVEL</constant>&nbsp;</entry>
                 <entry>enum&nbsp;v4l2_mpeg_video_h264_level</entry>
               </row>
@@ -1641,7 +1641,7 @@ Possible values are:</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-mpeg4-level">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_MPEG4_LEVEL</constant>&nbsp;</entry>
                 <entry>enum&nbsp;v4l2_mpeg_video_mpeg4_level</entry>
               </row>
@@ -1689,9 +1689,9 @@ Possible values are:</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-h264-profile">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_H264_PROFILE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_h264_profile</entry>
+                <entry>enum&nbsp;v4l2_mpeg_video_h264_profile</entry>
               </row>
               <row><entry spanname="descr">The profile information for H264.
 Applicable to the H264 encoder.
@@ -1774,9 +1774,9 @@ Possible values are:</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-mpeg4-profile">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_MPEG4_PROFILE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_mpeg4_profile</entry>
+                <entry>enum&nbsp;v4l2_mpeg_video_mpeg4_profile</entry>
               </row>
               <row><entry spanname="descr">The profile information for MPEG4.
 Applicable to the MPEG4 encoder.
@@ -1820,9 +1820,9 @@ Applicable to the encoder.
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-multi-slice-mode">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_MULTI_SLICE_MODE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_multi_slice_mode</entry>
+                <entry>enum&nbsp;v4l2_mpeg_video_multi_slice_mode</entry>
               </row>
               <row><entry spanname="descr">Determines how the encoder should handle division of frame into slices.
 Applicable to the encoder.
@@ -1868,9 +1868,9 @@ Applicable to the encoder.</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-h264-loop-filter-mode">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_H264_LOOP_FILTER_MODE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_h264_loop_filter_mode</entry>
+                <entry>enum&nbsp;v4l2_mpeg_video_h264_loop_filter_mode</entry>
               </row>
               <row><entry spanname="descr">Loop filter mode for H264 encoder.
 Possible values are:</entry>
@@ -1913,9 +1913,9 @@ Applicable to the H264 encoder.</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-h264-entropy-mode">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_H264_ENTROPY_MODE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_h264_symbol_mode</entry>
+                <entry>enum&nbsp;v4l2_mpeg_video_h264_entropy_mode</entry>
               </row>
               <row><entry spanname="descr">Entropy coding mode for H264 - CABAC/CAVALC.
 Applicable to the H264 encoder.
@@ -2140,9 +2140,9 @@ previous frames. Applicable to the H264 encoder.</entry>
               </row>
 
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-video-header-mode">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_VIDEO_HEADER_MODE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_header_mode</entry>
+                <entry>enum&nbsp;v4l2_mpeg_video_header_mode</entry>
               </row>
               <row><entry spanname="descr">Determines whether the header is returned as the first buffer or is
 it returned together with the first frame. Applicable to encoders.
@@ -2320,9 +2320,9 @@ Valid only when H.264 and macroblock level RC is enabled (<constant>V4L2_CID_MPE
 Applicable to the H264 encoder.</entry>
               </row>
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-mfc51-video-frame-skip-mode">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_MFC51_VIDEO_FRAME_SKIP_MODE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_mfc51_frame_skip_mode</entry>
+                <entry>enum&nbsp;v4l2_mpeg_mfc51_video_frame_skip_mode</entry>
               </row>
               <row><entry spanname="descr">
 Indicates in what conditions the encoder should skip frames. If encoding a frame would cause the encoded stream to be larger then
@@ -2361,9 +2361,9 @@ the stream will meet tight bandwidth contraints. Applicable to encoders.
 </entry>
               </row>
               <row><entry></entry></row>
-              <row>
+              <row id="v4l2-mpeg-mfc51-video-force-frame-type">
                 <entry spanname="id"><constant>V4L2_CID_MPEG_MFC51_VIDEO_FORCE_FRAME_TYPE</constant>&nbsp;</entry>
-                <entry>enum&nbsp;v4l2_mpeg_mfc51_force_frame_type</entry>
+                <entry>enum&nbsp;v4l2_mpeg_mfc51_video_force_frame_type</entry>
               </row>
               <row><entry spanname="descr">Force a frame type for the next queued buffer. Applicable to encoders.
 Possible values are:</entry>
diff --git a/Documentation/cgroups/memory.txt b/Documentation/cgroups/memory.txt
index 6f3c598971fc..06eb6d957c83 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -380,7 +380,7 @@ will be charged as a new owner of it.
 
 5.2 stat file
 
-5.2.1 memory.stat file includes following statistics
+memory.stat file includes following statistics
 
 # per-memory cgroup local status
 cache           - # of bytes of page cache memory.
@@ -438,89 +438,6 @@ Note:
          file_mapped is accounted only when the memory cgroup is owner of page
          cache.)
 
-5.2.2 memory.vmscan_stat
-
-memory.vmscan_stat includes statistics information for memory scanning and
-freeing, reclaiming. The statistics shows memory scanning information since
-memory cgroup creation and can be reset to 0 by writing 0 as
-
- #echo 0 > ../memory.vmscan_stat
-
-This file contains following statistics.
-
-[param]_[file_or_anon]_pages_by_[reason]_[under_heararchy]
-[param]_elapsed_ns_by_[reason]_[under_hierarchy]
-
-For example,
-
-  scanned_file_pages_by_limit indicates the number of scanned
-  file pages at vmscan.
-
-Now, 3 parameters are supported
-
-  scanned - the number of pages scanned by vmscan
-  rotated - the number of pages activated at vmscan
-  freed   - the number of pages freed by vmscan
-
-If "rotated" is high against scanned/freed, the memcg seems busy.
-
-Now, 2 reason are supported
-
-  limit - the memory cgroup's limit
-  system - global memory pressure + softlimit
-           (global memory pressure not under softlimit is not handled now)
-
-When under_hierarchy is added in the tail, the number indicates the
-total memcg scan of its children and itself.
-
-elapsed_ns is a elapsed time in nanosecond. This may include sleep time
-and not indicates CPU usage. So, please take this as just showing
-latency.
-
-Here is an example.
-
-# cat /cgroup/memory/A/memory.vmscan_stat
-scanned_pages_by_limit 9471864
-scanned_anon_pages_by_limit 6640629
-scanned_file_pages_by_limit 2831235
-rotated_pages_by_limit 4243974
-rotated_anon_pages_by_limit 3971968
-rotated_file_pages_by_limit 272006
-freed_pages_by_limit 2318492
-freed_anon_pages_by_limit 962052
-freed_file_pages_by_limit 1356440
-elapsed_ns_by_limit 351386416101
-scanned_pages_by_system 0
-scanned_anon_pages_by_system 0
-scanned_file_pages_by_system 0
-rotated_pages_by_system 0
-rotated_anon_pages_by_system 0
-rotated_file_pages_by_system 0
-freed_pages_by_system 0
-freed_anon_pages_by_system 0
-freed_file_pages_by_system 0
-elapsed_ns_by_system 0
-scanned_pages_by_limit_under_hierarchy 9471864
-scanned_anon_pages_by_limit_under_hierarchy 6640629
-scanned_file_pages_by_limit_under_hierarchy 2831235
-rotated_pages_by_limit_under_hierarchy 4243974
-rotated_anon_pages_by_limit_under_hierarchy 3971968
-rotated_file_pages_by_limit_under_hierarchy 272006
-freed_pages_by_limit_under_hierarchy 2318492
-freed_anon_pages_by_limit_under_hierarchy 962052
-freed_file_pages_by_limit_under_hierarchy 1356440
-elapsed_ns_by_limit_under_hierarchy 351386416101
-scanned_pages_by_system_under_hierarchy 0
-scanned_anon_pages_by_system_under_hierarchy 0
-scanned_file_pages_by_system_under_hierarchy 0
-rotated_pages_by_system_under_hierarchy 0
-rotated_anon_pages_by_system_under_hierarchy 0
-rotated_file_pages_by_system_under_hierarchy 0
-freed_pages_by_system_under_hierarchy 0
-freed_anon_pages_by_system_under_hierarchy 0
-freed_file_pages_by_system_under_hierarchy 0
-elapsed_ns_by_system_under_hierarchy 0
-
 5.3 swappiness
 
 Similar to /proc/sys/vm/swappiness, but affecting a hierarchy of groups only.
diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
index c4a6e148732a..4dc465477665 100644
--- a/Documentation/feature-removal-schedule.txt
+++ b/Documentation/feature-removal-schedule.txt
@@ -592,3 +592,11 @@ Why:    In 3.0, we can now autodetect internal 3G device and already have
         interface that was used by acer-wmi driver. It will replaced by
         information log when acer-wmi initial.
 Who:    Lee, Chun-Yi <jlee@novell.com>
+
+----------------------------
+What:   The XFS nodelaylog mount option
+When:   3.3
+Why:    The delaylog mode that has been the default since 2.6.39 has proven
+        stable, and the old code is in the way of additional improvements in
+        the log code.
+Who:    Christoph Hellwig <hch@lst.de>
diff --git a/Documentation/hwmon/coretemp b/Documentation/hwmon/coretemp
index fa8776ab9b18..84d46c0c71a3 100644
--- a/Documentation/hwmon/coretemp
+++ b/Documentation/hwmon/coretemp
@@ -35,13 +35,6 @@ the Out-Of-Spec bit. Following table summarizes the exported sysfs files:
 All Sysfs entries are named with their core_id (represented here by 'X').
 tempX_input      - Core temperature (in millidegrees Celsius).
 tempX_max        - All cooling devices should be turned on (on Core2).
-                   Initialized with IA32_THERM_INTERRUPT. When the CPU
-                   temperature reaches this temperature, an interrupt is
-                   generated and tempX_max_alarm is set.
-tempX_max_hyst   - If the CPU temperature falls below than temperature,
-                   an interrupt is generated and tempX_max_alarm is reset.
-tempX_max_alarm  - Set if the temperature reaches or exceeds tempX_max.
-                   Reset if the temperature drops to or below tempX_max_hyst.
 tempX_crit       - Maximum junction temperature (in millidegrees Celsius).
 tempX_crit_alarm - Set when Out-of-spec bit is set, never clears.
                    Correct CPU operation is no longer guaranteed.
@@ -49,9 +42,10 @@ tempX_label	 - Contains string "Core X", where X is processor
                    number. For Package temp, this will be "Physical id Y",
                    where Y is the package number.
 
-The TjMax temperature is set to 85 degrees C if undocumented model specific
-register (UMSR) 0xee has bit 30 set. If not the TjMax is 100 degrees C as
-(sometimes) documented in processor datasheet.
+On CPU models which support it, TjMax is read from a model-specific register.
+On other models, it is set to an arbitrary value based on weak heuristics.
+If these heuristics don't work for you, you can pass the correct TjMax value
+as a module parameter (tjmax).
 
 Appendix A. Known TjMax lists (TBD):
 Some information comes from ark.intel.com
diff --git a/Documentation/hwmon/max16065 b/Documentation/hwmon/max16065
index 44b4f61e04f9..c11f64a1f2ad 100644
--- a/Documentation/hwmon/max16065
+++ b/Documentation/hwmon/max16065
@@ -62,6 +62,13 @@ can be safely used to identify the chip. You will have to instantiate
 the devices explicitly. Please see Documentation/i2c/instantiating-devices for
 details.
 
+WARNING: Do not access chip registers using the i2cdump command, and do not use
+any of the i2ctools commands on a command register (0xa5 to 0xac). The chips
+supported by this driver interpret any access to a command register (including
+read commands) as request to execute the command in question. This may result in
+power loss, board resets, and/or Flash corruption. Worst case, your board may
+turn into a brick.
+
 
 Sysfs entries
 -------------
diff --git a/Documentation/ioctl/ioctl-number.txt b/Documentation/ioctl/ioctl-number.txt
index 845a191004b1..54078ed96b37 100644
--- a/Documentation/ioctl/ioctl-number.txt
+++ b/Documentation/ioctl/ioctl-number.txt
@@ -319,4 +319,6 @@ Code  Seq#(hex)	Include File		Comments
                                         <mailto:thomas@winischhofer.net>
 0xF4    00-1F   video/mbxfb.h           mbxfb
                                         <mailto:raph@8d.com>
+0xF6    all     LTTng                   Linux Trace Toolkit Next Generation
+                                        <mailto:mathieu.desnoyers@efficios.com>
 0xFD    all     linux/dm-ioctl.h
diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
index 614d0382e2cb..854ed5ca7e3f 100644
--- a/Documentation/kernel-parameters.txt
+++ b/Documentation/kernel-parameters.txt
@@ -2086,9 +2086,12 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
                         Override pmtimer IOPort with a hex value.
                         e.g. pmtmr=0x508
 
-        pnp.debug       [PNP]
-                        Enable PNP debug messages.  This depends on the
-                        CONFIG_PNP_DEBUG_MESSAGES option.
+        pnp.debug=1     [PNP]
+                        Enable PNP debug messages (depends on the
+                        CONFIG_PNP_DEBUG_MESSAGES option).  Change at run-time
+                        via /sys/module/pnp/parameters/debug.  We always show
+                        current resource usage; turning this on also shows
+                        possible settings and some assignment information.
 
         pnpacpi=        [ACPI]
                         { off }
diff --git a/Documentation/networking/00-INDEX b/Documentation/networking/00-INDEX
index 4edd78dfb362..bbce1215434a 100644
--- a/Documentation/networking/00-INDEX
+++ b/Documentation/networking/00-INDEX
@@ -1,13 +1,21 @@
 00-INDEX
         - this file
+3c359.txt
+        - information on the 3Com TokenLink Velocity XL (3c5359) driver.
 3c505.txt
         - information on the 3Com EtherLink Plus (3c505) driver.
+3c509.txt
+        - information on the 3Com Etherlink III Series Ethernet cards.
 6pack.txt
         - info on the 6pack protocol, an alternative to KISS for AX.25
 DLINK.txt
         - info on the D-Link DE-600/DE-620 parallel port pocket adapters
 PLIP.txt
         - PLIP: The Parallel Line Internet Protocol device driver
+README.ipw2100
+        - README for the Intel PRO/Wireless 2100 driver.
+README.ipw2200
+        - README for the Intel PRO/Wireless 2915ABG and 2200BG driver.
 README.sb1000
         - info on General Instrument/NextLevel SURFboard1000 cable modem.
 alias.txt
@@ -20,8 +28,12 @@ atm.txt
         - info on where to get ATM programs and support for Linux.
 ax25.txt
         - info on using AX.25 and NET/ROM code for Linux
+batman-adv.txt
+        - B.A.T.M.A.N routing protocol on top of layer 2 Ethernet Frames.
 baycom.txt
         - info on the driver for Baycom style amateur radio modems
+bonding.txt
+        - Linux Ethernet Bonding Driver HOWTO: link aggregation in Linux.
 bridge.txt
         - where to get user space programs for ethernet bridging with Linux.
 can.txt
@@ -34,32 +46,60 @@ cxacru.txt
         - Conexant AccessRunner USB ADSL Modem
 cxacru-cf.py
         - Conexant AccessRunner USB ADSL Modem configuration file parser
+cxgb.txt
+        - Release Notes for the Chelsio N210 Linux device driver.
+dccp.txt
+        - the Datagram Congestion Control Protocol (DCCP) (RFC 4340..42).
 de4x5.txt
         - the Digital EtherWORKS DE4?? and DE5?? PCI Ethernet driver
 decnet.txt
         - info on using the DECnet networking layer in Linux.
 depca.txt
         - the Digital DEPCA/EtherWORKS DE1?? and DE2?? LANCE Ethernet driver
+dl2k.txt
+        - README for D-Link DL2000-based Gigabit Ethernet Adapters (dl2k.ko).
+dm9000.txt
+        - README for the Simtec DM9000 Network driver.
 dmfe.txt
         - info on the Davicom DM9102(A)/DM9132/DM9801 fast ethernet driver.
+dns_resolver.txt
+        - The DNS resolver module allows kernel servies to make DNS queries.
+driver.txt
+        - Softnet driver issues.
 e100.txt
         - info on Intel's EtherExpress PRO/100 line of 10/100 boards
 e1000.txt
         - info on Intel's E1000 line of gigabit ethernet boards
+e1000e.txt
+        - README for the Intel Gigabit Ethernet Driver (e1000e).
 eql.txt
         - serial IP load balancing
 ewrk3.txt
         - the Digital EtherWORKS 3 DE203/4/5 Ethernet driver
+fib_trie.txt
+        - Level Compressed Trie (LC-trie) notes: a structure for routing.
 filter.txt
         - Linux Socket Filtering
 fore200e.txt
         - FORE Systems PCA-200E/SBA-200E ATM NIC driver info.
 framerelay.txt
         - info on using Frame Relay/Data Link Connection Identifier (DLCI).
+gen_stats.txt
+        - Generic networking statistics for netlink users.
+generic_hdlc.txt
+        - The generic High Level Data Link Control (HDLC) layer.
 generic_netlink.txt
         - info on Generic Netlink
+gianfar.txt
+        - Gianfar Ethernet Driver.
 ieee802154.txt
         - Linux IEEE 802.15.4 implementation, API and drivers
+ifenslave.c
+        - Configure network interfaces for parallel routing (bonding).
+igb.txt
+        - README for the Intel Gigabit Ethernet Driver (igb).
+igbvf.txt
+        - README for the Intel Gigabit Ethernet Driver (igbvf).
 ip-sysctl.txt
         - /proc/sys/net/ipv4/* variables
 ip_dynaddr.txt
@@ -68,41 +108,117 @@ ipddp.txt
         - AppleTalk-IP Decapsulation and AppleTalk-IP Encapsulation
 iphase.txt
         - Interphase PCI ATM (i)Chip IA Linux driver info.
+ipv6.txt
+        - Options to the ipv6 kernel module.
+ipvs-sysctl.txt
+        - Per-inode explanation of the /proc/sys/net/ipv4/vs interface.
 irda.txt
         - where to get IrDA (infrared) utilities and info for Linux.
+ixgb.txt
+        - README for the Intel 10 Gigabit Ethernet Driver (ixgb).
+ixgbe.txt
+        - README for the Intel 10 Gigabit Ethernet Driver (ixgbe).
+ixgbevf.txt
+        - README for the Intel Virtual Function (VF) Driver (ixgbevf).
+l2tp.txt
+        - User guide to the L2TP tunnel protocol.
 lapb-module.txt
         - programming information of the LAPB module.
 ltpc.txt
         - the Apple or Farallon LocalTalk PC card driver
+mac80211-injection.txt
+        - HOWTO use packet injection with mac80211
 multicast.txt
         - Behaviour of cards under Multicast
+multiqueue.txt
+        - HOWTO for multiqueue network device support.
+netconsole.txt
+        - The network console module netconsole.ko: configuration and notes.
+netdev-features.txt
+        - Network interface features API description.
 netdevices.txt
         - info on network device driver functions exported to the kernel.
+netif-msg.txt
+        - Design of the network interface message level setting (NETIF_MSG_*).
+nfc.txt
+        - The Linux Near Field Communication (NFS) subsystem.
 olympic.txt
         - IBM PCI Pit/Pit-Phy/Olympic Token Ring driver info.
+operstates.txt
+        - Overview of network interface operational states.
+packet_mmap.txt
+        - User guide to memory mapped packet socket rings (PACKET_[RT]X_RING).
+phonet.txt
+        - The Phonet packet protocol used in Nokia cellular modems.
+phy.txt
+        - The PHY abstraction layer.
+pktgen.txt
+        - User guide to the kernel packet generator (pktgen.ko).
 policy-routing.txt
         - IP policy-based routing
+ppp_generic.txt
+        - Information about the generic PPP driver.
+proc_net_tcp.txt
+        - Per inode overview of the /proc/net/tcp and /proc/net/tcp6 interfaces.
+radiotap-headers.txt
+        - Background on radiotap headers.
 ray_cs.txt
         - Raylink Wireless LAN card driver info.
+rds.txt
+        - Background on the reliable, ordered datagram delivery method RDS.
+regulatory.txt
+        - Overview of the Linux wireless regulatory infrastructure.
+rxrpc.txt
+        - Guide to the RxRPC protocol.
+s2io.txt
+        - Release notes for Neterion Xframe I/II 10GbE driver.
+scaling.txt
+        - Explanation of network scaling techniques: RSS, RPS, RFS, aRFS, XPS.
+sctp.txt
+        - Notes on the Linux kernel implementation of the SCTP protocol.
+secid.txt
+        - Explanation of the secid member in flow structures.
 skfp.txt
         - SysKonnect FDDI (SK-5xxx, Compaq Netelligent) driver info.
 smc9.txt
         - the driver for SMC's 9000 series of Ethernet cards
 smctr.txt
         - SMC TokenCard TokenRing Linux driver info.
+spider-net.txt
+        - README for the Spidernet Driver (as found in PS3 / Cell BE).
+stmmac.txt
+        - README for the STMicro Synopsys Ethernet driver.
+tc-actions-env-rules.txt
+        - rules for traffic control (tc) actions.
+timestamping.txt
+        - overview of network packet timestamping variants.
 tcp.txt
         - short blurb on how TCP output takes place.
+tcp-thin.txt
+        - kernel tuning options for low rate 'thin' TCP streams.
 tlan.txt
         - ThunderLAN (Compaq Netelligent 10/100, Olicom OC-2xxx) driver info.
 tms380tr.txt
         - SysKonnect Token Ring ISA/PCI adapter driver info.
+tproxy.txt
+        - Transparent proxy support user guide.
 tuntap.txt
         - TUN/TAP device driver, allowing user space Rx/Tx of packets.
+udplite.txt
+        - UDP-Lite protocol (RFC 3828) introduction.
 vortex.txt
         - info on using 3Com Vortex (3c590, 3c592, 3c595, 3c597) Ethernet cards.
+vxge.txt
+        - README for the Neterion X3100 PCIe Server Adapter.
 x25.txt
         - general info on X.25 development.
 x25-iface.txt
         - description of the X.25 Packet Layer to LAPB device interface.
+xfrm_proc.txt
+        - description of the statistics package for XFRM.
+xfrm_sync.txt
+        - sync patches for XFRM enable migration of an SA between hosts.
+xfrm_sysctl.txt
+        - description of the XFRM configuration options.
 z8530drv.txt
         - info about Linux driver for Z8530 based HDLC cards for AX.25
diff --git a/Documentation/networking/dmfe.txt b/Documentation/networking/dmfe.txt
index 8006c227fda2..25320bf19c86 100644
--- a/Documentation/networking/dmfe.txt
+++ b/Documentation/networking/dmfe.txt
@@ -1,3 +1,5 @@
+Note: This driver doesn't have a maintainer.
+
 Davicom DM9102(A)/DM9132/DM9801 fast ethernet driver for Linux.
 
 This program is free software; you can redistribute it and/or
@@ -55,7 +57,6 @@ Test and make sure PCI latency is now correct for all cases.
 Authors:
 
 Sten Wang <sten_wang@davicom.com.tw >   : Original Author
-Tobias Ringstrom <tori@unhappy.mine.nu> : Current Maintainer
 
 Contributors:
 
diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index db2a4067013c..ca5cdcd0f0e3 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -992,7 +992,7 @@ bindv6only - BOOLEAN
                 TRUE: disable IPv4-mapped address feature
                 FALSE: enable IPv4-mapped address feature
 
-        Default: FALSE (as specified in RFC2553bis)
+        Default: FALSE (as specified in RFC3493)
 
 IPv6 Fragmentation:
 
@@ -1042,7 +1042,7 @@ conf/interface/*:
         The functional behaviour for certain settings is different
         depending on whether local forwarding is enabled or not.
 
-accept_ra - BOOLEAN
+accept_ra - INTEGER
         Accept Router Advertisements; autoconfigure using them.
 
         Possible values are:
@@ -1106,7 +1106,7 @@ dad_transmits - INTEGER
         The amount of Duplicate Address Detection probes to send.
         Default: 1
 
-forwarding - BOOLEAN
+forwarding - INTEGER
         Configure interface-specific Host/Router behaviour.
 
         Note: It is recommended to have the same setting on all
diff --git a/Documentation/networking/scaling.txt b/Documentation/networking/scaling.txt
index 7254b4b5910e..8ce7c30e7230 100644
--- a/Documentation/networking/scaling.txt
+++ b/Documentation/networking/scaling.txt
@@ -52,7 +52,8 @@ module parameter for specifying the number of hardware queues to
 configure. In the bnx2x driver, for instance, this parameter is called
 num_queues. A typical RSS configuration would be to have one receive queue
 for each CPU if the device supports enough queues, or otherwise at least
-one for each cache domain at a particular cache level (L1, L2, etc.).
+one for each memory domain, where a memory domain is a set of CPUs that
+share a particular memory level (L1, L2, NUMA node, etc.).
 
 The indirection table of an RSS device, which resolves a queue by masked
 hash, is usually programmed by the driver at initialization. The
@@ -82,11 +83,17 @@ RSS should be enabled when latency is a concern or whenever receive
 interrupt processing forms a bottleneck. Spreading load between CPUs
 decreases queue length. For low latency networking, the optimal setting
 is to allocate as many queues as there are CPUs in the system (or the
-NIC maximum, if lower). Because the aggregate number of interrupts grows
-with each additional queue, the most efficient high-rate configuration
+NIC maximum, if lower). The most efficient high-rate configuration
 is likely the one with the smallest number of receive queues where no
-CPU that processes receive interrupts reaches 100% utilization. Per-cpu
-load can be observed using the mpstat utility.
+receive queue overflows due to a saturated CPU, because in default
+mode with interrupt coalescing enabled, the aggregate number of
+interrupts (and thus work) grows with each additional queue.
+
+Per-cpu load can be observed using the mpstat utility, but note that on
+processors with hyperthreading (HT), each hyperthread is represented as
+a separate CPU. For interrupt handling, HT has shown no benefit in
+initial tests, so limit the number of queues to the number of CPU cores
+in the system.
 
 
 RPS: Receive Packet Steering
@@ -145,7 +152,7 @@ the bitmap.
 == Suggested Configuration
 
 For a single queue device, a typical RPS configuration would be to set
-the rps_cpus to the CPUs in the same cache domain of the interrupting
+the rps_cpus to the CPUs in the same memory domain of the interrupting
 CPU. If NUMA locality is not an issue, this could also be all CPUs in
 the system. At high interrupt rate, it might be wise to exclude the
 interrupting CPU from the map since that already performs much work.
@@ -154,7 +161,7 @@ For a multi-queue system, if RSS is configured so that a hardware
 receive queue is mapped to each CPU, then RPS is probably redundant
 and unnecessary. If there are fewer hardware queues than CPUs, then
 RPS might be beneficial if the rps_cpus for each queue are the ones that
-share the same cache domain as the interrupting CPU for that queue.
+share the same memory domain as the interrupting CPU for that queue.
 
 
 RFS: Receive Flow Steering
@@ -236,7 +243,7 @@ configured. The number of entries in the global flow table is set through:
 
 The number of entries in the per-queue flow table are set through:
 
- /sys/class/net/<dev>/queues/tx-<n>/rps_flow_cnt
+ /sys/class/net/<dev>/queues/rx-<n>/rps_flow_cnt
 
 == Suggested Configuration
 
@@ -326,7 +333,7 @@ The queue chosen for transmitting a particular flow is saved in the
 corresponding socket structure for the flow (e.g. a TCP connection).
 This transmit queue is used for subsequent packets sent on the flow to
 prevent out of order (ooo) packets. The choice also amortizes the cost
-of calling get_xps_queues() over all packets in the connection. To avoid
+of calling get_xps_queues() over all packets in the flow. To avoid
 ooo packets, the queue for a flow can subsequently only be changed if
 skb->ooo_okay is set for a packet in the flow. This flag indicates that
 there are no outstanding packets in the flow, so the transmit queue can
diff --git a/Documentation/power/runtime_pm.txt b/Documentation/power/runtime_pm.txt
index 4ce5450ab6e8..6066e3a6b9a9 100644
--- a/Documentation/power/runtime_pm.txt
+++ b/Documentation/power/runtime_pm.txt
@@ -431,8 +431,7 @@ drivers/base/power/runtime.c and include/linux/pm_runtime.h:
 
   void pm_runtime_irq_safe(struct device *dev);
     - set the power.irq_safe flag for the device, causing the runtime-PM
-      suspend and resume callbacks (but not the idle callback) to be invoked
-      with interrupts disabled
+      callbacks to be invoked with interrupts off
 
   void pm_runtime_mark_last_busy(struct device *dev);
     - set the power.last_busy field to the current time
diff --git a/Documentation/vm/transhuge.txt b/Documentation/vm/transhuge.txt
index 0924aaca3302..29bdf62aac09 100644
--- a/Documentation/vm/transhuge.txt
+++ b/Documentation/vm/transhuge.txt
@@ -123,10 +123,11 @@ be automatically shutdown if it's set to "never".
 khugepaged runs usually at low frequency so while one may not want to
 invoke defrag algorithms synchronously during the page faults, it
 should be worth invoking defrag at least in khugepaged. However it's
-also possible to disable defrag in khugepaged:
+also possible to disable defrag in khugepaged by writing 0 or enable
+defrag in khugepaged by writing 1:
 
-echo yes >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
-echo no >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
+echo 0 >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
+echo 1 >/sys/kernel/mm/transparent_hugepage/khugepaged/defrag
 
 You can also control how many pages khugepaged should scan at each
 pass: