Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable

.gitignore

@@ -22,19 +22,16 @@
 *.lst
 *.symtypes
 *.order
+modules.builtin
 *.elf
 *.bin
 *.gz
 *.bz2
 *.lzma
 *.xz
-*.lz4
 *.lzo
 *.patch
 *.gcno
-modules.builtin
-Module.symvers
-*.dwo
 
 #
 # Top-level generic files
@@ -46,6 +43,7 @@ Module.symvers
 /vmlinuz
 /System.map
 /Module.markers
+/Module.symvers
 
 #
 # Debian directory (make deb-pkg)
@@ -62,6 +60,7 @@ Module.symvers
 # Generated include files
 #
 include/config
+include/linux/version.h
 include/generated
 arch/*/include/generated
 
@@ -85,14 +84,3 @@ GTAGS
 *.orig
 *~
 \#*#
-
-#
-# Leavings from module signing
-#
-extra_certificates
-signing_key.priv
-signing_key.x509
-x509.genkey
-
-# Kconfig presets
-all.config

.mailmap

@@ -62,11 +62,6 @@ Jeff Garzik <jgarzik@pretzel.yyz.us>
 Jens Axboe <axboe@suse.de>
 Jens Osterkamp <Jens.Osterkamp@de.ibm.com>
 John Stultz <johnstul@us.ibm.com>
-<josh@joshtriplett.org> <josh@freedesktop.org>
-<josh@joshtriplett.org> <josh@kernel.org>
-<josh@joshtriplett.org> <josht@linux.vnet.ibm.com>
-<josh@joshtriplett.org> <josht@us.ibm.com>
-<josh@joshtriplett.org> <josht@vnet.ibm.com>
 Juha Yrjola <at solidboot.com>
 Juha Yrjola <juha.yrjola@nokia.com>
 Juha Yrjola <juha.yrjola@solidboot.com>
@@ -104,7 +99,6 @@ Sachin P Sant <ssant@in.ibm.com>
 Sam Ravnborg <sam@mars.ravnborg.org>
 Sascha Hauer <s.hauer@pengutronix.de>
 S.Çağlar Onur <caglar@pardus.org.tr>
-Shiraz Hashim <shiraz.linux.kernel@gmail.com> <shiraz.hashim@st.com>
 Simon Kelley <simon@thekelleys.org.uk>
 Stéphane Witzmann <stephane.witzmann@ubpmes.univ-bpclermont.fr>
 Stephen Hemminger <shemminger@osdl.org>
@@ -117,8 +111,5 @@ Uwe Kleine-König <ukleinek@informatik.uni-freiburg.de>
 Uwe Kleine-König <ukl@pengutronix.de>
 Uwe Kleine-König <Uwe.Kleine-Koenig@digi.com>
 Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
-Viresh Kumar <viresh.linux@gmail.com> <viresh.kumar@st.com>
 Takashi YOSHII <takashi.yoshii.zj@renesas.com>
 Yusuke Goda <goda.yusuke@renesas.com>
-Gustavo Padovan <gustavo@las.ic.unicamp.br>
-Gustavo Padovan <padovan@profusion.mobi>

CREDITS

@@ -9,10 +9,6 @@
 			Linus
 ----------
 
-M: Matt Mackal
-E: mpm@selenic.com
-D: SLOB slab allocator
-
 N: Matti Aarnio
 E: mea@nic.funet.fi
 D: Alpha systems hacking, IPv6 and other network related stuff
@@ -518,11 +514,6 @@ S: Bessemerstraat 21
 S: Amsterdam
 S: The Netherlands
 
-N: NeilBrown
-E: neil@brown.name
-P: 4096R/566281B9 1BC6 29EB D390 D870 7B5F  497A 39EC 9EDD 5662 81B9
-D: NFSD Maintainer 2000-2007
-
 N: Zach Brown
 E: zab@zabbo.net
 D: maestro pci sound
@@ -634,13 +625,6 @@ N: Michael Elizabeth Chastain
 E: mec@shout.net
 D: Configure, Menuconfig, xconfig
 
-N: Mauro Carvalho Chehab
-E: m.chehab@samsung.org
-E: mchehab@infradead.org
-D: Media subsystem (V4L/DVB) drivers and core
-D: EDAC drivers and EDAC 3.0 core rework
-S: Brazil
-
 N: Raymond Chen
 E: raymondc@microsoft.com
 D: Author of Configure script
@@ -648,13 +632,14 @@ S: 14509 NE 39th Street #1096
 S: Bellevue, Washington 98007
 S: USA
 
-N: Chris Cheney
-E: chris.cheney@gmail.com
-E: ccheney@redhat.com
+N: Christopher L. Cheney
+E: ccheney@debian.org
+E: ccheney@cheney.cx
+W: http://www.cheney.cx
 P: 1024D/8E384AF2 2D31 1927 87D7 1F24 9FF9  1BC5 D106 5AB3 8E38 4AF2
 D: Vista Imaging usb webcam driver
-S: 2308 Therrell Way
-S: McKinney, TX 75070
+S: 314 Prince of Wales
+S: Conroe, TX 77304
 S: USA
 
 N: Stuart Cheshire
@@ -666,11 +651,6 @@ S: Stanford University
 S: Stanford, California 94305
 S: USA
 
-N: Carlos Chinea
-E: carlos.chinea@nokia.com
-E: cch.devel@gmail.com
-D: Author of HSI Subsystem
-
 N: Randolph Chung
 E: tausq@debian.org
 D: Linux/PA-RISC hacker
@@ -776,10 +756,6 @@ S: Northampton
 S: NN1 3QT
 S: United Kingdom
 
-N: Massimo Dal Zotto
-E: dz@debian.org
-D: i8k Dell laptop SMM driver
-
 N: Uwe Dannowski
 E: Uwe.Dannowski@ira.uka.de
 W: http://i30www.ira.uka.de/~dannowsk/
@@ -834,8 +810,8 @@ S: D-69231 Rauenberg
 S: Germany
 
 N: Jean Delvare
-E: jdelvare@suse.de
-W: http://jdelvare.nerim.net/
+E: khali@linux-fr.org
+W: http://khali.linux-fr.org/
 D: Several hardware monitoring drivers
 S: France
 
@@ -972,11 +948,11 @@ S: Blacksburg, Virginia 24061
 S: USA
 
 N: Randy Dunlap
-E: rdunlap@infradead.org
-W: http://www.infradead.org/~rdunlap/
+E: rdunlap@xenotime.net
+W: http://www.xenotime.net/linux/linux.html
+W: http://www.linux-usb.org
 D: Linux-USB subsystem, USB core/UHCI/printer/storage drivers
 D: x86 SMP, ACPI, bootflag hacking
-D: documentation, builds
 S: (ask for current address)
 S: USA
 
@@ -1135,7 +1111,6 @@ D: author of userfs filesystem
 D: Improved mmap and munmap handling
 D: General mm minor tidyups
 D: autofs v4 maintainer
-D: Xen subsystem
 S: 987 Alabama St
 S: San Francisco
 S: CA, 94110
@@ -1240,7 +1215,7 @@ E: philip@gladstonefamily.net
 D: Kernel / timekeeping stuff
 S: Carlisle, MA 01741
 S: USA
-
+  
 N: Jan-Benedict Glaw
 E: jbglaw@lug-owl.de
 D: SRM environment driver (for Alpha systems)
@@ -1381,9 +1356,6 @@ S: 17 rue Danton
 S: F - 94270 Le Kremlin-Bicêtre
 S: France
 
-N: Jack Hammer
-D: IBM ServeRAID RAID (ips) driver maintenance
-
 N: Greg Hankins
 E: gregh@cc.gatech.edu
 D: fixed keyboard driver to separate LED and locking status
@@ -1533,14 +1505,6 @@ D: Natsemi ethernet
 D: Cobalt Networks (x86) support
 D: This-and-That
 
-N: Mark M. Hoffman
-E: mhoffman@lightlink.com
-D: asb100, lm93 and smsc47b397 hardware monitoring drivers
-D: hwmon subsystem core
-D: hwmon subsystem maintainer
-D: i2c-sis96x and i2c-stub SMBus drivers
-S: USA
-
 N: Dirk Hohndel
 E: hohndel@suse.de
 D: The XFree86[tm] Project
@@ -1603,12 +1567,12 @@ S: Wantage, New Jersey 07461
 S: USA
 
 N: Harald Hoyer
-E: harald@redhat.com
-W: http://www.harald-hoyer.de
+E: harald.hoyer@parzelle.de
+W: http://parzelle.de/
 D: ip_masq_quake
 D: md boot support
-S: Am Strand 5
-S: D-19063 Schwerin
+S: Hohe Strasse 30
+S: D-70176 Stuttgart
 S: Germany
 
 N: Jan Hubicka
@@ -1694,10 +1658,6 @@ S: Reading
 S: RG6 2NU
 S: United Kingdom
 
-N: Dave Jeffery
-E: dhjeffery@gmail.com
-D: SCSI hacks and IBM ServeRAID RAID driver maintenance
-
 N: Jakub Jelinek
 E: jakub@redhat.com
 W: http://sunsite.mff.cuni.cz/~jj
@@ -1858,11 +1818,6 @@ S: Kattreinstr 38
 S: D-64295
 S: Germany
 
-N: Avi Kivity
-E: avi.kivity@gmail.com
-D: Kernel-based Virtual Machine (KVM)
-S: Ra'annana, Israel
-
 N: Andi Kleen
 E: andi@firstfloor.org
 U: http://www.halobates.de
@@ -2578,14 +2533,10 @@ S: 22 Seaview St
 S: Fullarton 5063
 S: South Australia
 
-N: Wolfgang Muees
+N. Wolfgang Muees
 E: wolfgang@iksw-muees.de
 D: Auerswald USB driver
 
-N: Paul Mundt
-E: paul.mundt@gmail.com
-D: SuperH maintainer
-
 N: Ian A. Murdock
 E: imurdock@gnu.ai.mit.edu
 D: Creator of Debian distribution
@@ -2603,7 +2554,7 @@ S: Toronto, Ontario
 S: Canada
 
 N: Zwane Mwaikambo
-E: zwanem@gmail.com
+E: zwane@arm.linux.org.uk
 D: Various driver hacking
 D: Lowlevel x86 kernel hacking
 D: General debugging
@@ -2729,9 +2680,6 @@ N: Greg Page
 E: gpage@sovereign.org
 D: IPX development and support
 
-N: Venkatesh Pallipadi (Venki)
-D: x86/HPET
-
 N: David Parsons
 E: orc@pell.chi.il.us
 D: improved memory detection code.
@@ -2838,7 +2786,8 @@ S: Ottawa, Ontario
 S: Canada K2P 0X8
 
 N: Mikael Pettersson
-E: mikpelinux@gmail.com
+E: mikpe@it.uu.se
+W: http://user.it.uu.se/~mikpe/linux/
 D: Miscellaneous fixes
 
 N: Reed H. Petty
@@ -2925,11 +2874,6 @@ S: Framewood Road
 S: Wexham SL3 6PJ
 S: United Kingdom
 
-N: Richard Purdie
-E: rpurdie@rpsys.net
-D: Backlight subsystem maintainer
-S: United Kingdom
-
 N: Daniel Quinlan
 E: quinlan@pathname.com
 W: http://www.pathname.com/~quinlan/
@@ -3187,11 +3131,6 @@ N: Dipankar Sarma
 E: dipankar@in.ibm.com
 D: RCU
 
-N: Yoshinori Sato
-E: ysato@users.sourceforge.jp
-D: uClinux for Renesas H8/300 (H8300)
-D: http://uclinux-h8.sourceforge.jp/
-
 N: Hannu Savolainen
 E: hannu@opensound.com
 D: Maintainer of the sound drivers until 2.1.x days.
@@ -3518,11 +3457,10 @@ S: MacGregor A.C.T 2615
 S: Australia
 
 N: Josh Triplett
-E: josh@joshtriplett.org
-P: 4096R/8AFF873D 758E 5042 E397 4BA3 3A9C  1E67 0ED9 A3DF 8AFF 873D
-D: RCU and rcutorture
+E: josh@freedesktop.org
+P: 1024D/D0FE7AFB B24A 65C9 1D71 2AC2 DE87  CA26 189B 9946 D0FE 7AFB
+D: rcutorture maintainer
 D: lock annotations, finding and fixing lock bugs
-D: kernel tinification
 
 N: Winfried Trümper
 E: winni@xpilot.org
@@ -3871,8 +3809,8 @@ D: INFO-SHEET, former maintainer
 D: Author of the longest-living linux bug
 
 N: Jonathan Woithe
-E: jwoithe@just42.net
-W: http:/www.just42.net/jwoithe
+E: jwoithe@physics.adelaide.edu.au
+W: http://www.physics.adelaide.edu.au/~jwoithe
 D: ALS-007 sound card extensions to Sound Blaster driver
 S: 20 Jordan St
 S: Valley View, SA 5093

Documentation/.gitignore

@@ -0,0 +1,7 @@
+filesystems/dnotify_test
+laptops/dslm
+timers/hpet_example
+vm/hugepage-mmap
+vm/hugepage-shm
+vm/map_hugetlb
+

Documentation/00-INDEX

@@ -2,13 +2,13 @@
 This is a brief list of all the files in ./linux/Documentation and what
 they contain. If you add a documentation file, please list it here in
 alphabetical order as well, or risk being hunted down like a rabid dog.
-Please keep the descriptions small enough to fit on one line.
+Please try and keep the descriptions small enough to fit on one line.
 							 Thanks -- Paul G.
 
 Following translations are available on the WWW:
 
-   - Japanese, maintained by the JF Project (jf@listserv.linux.or.jp), at
-     http://linuxjf.sourceforge.jp/
+   - Japanese, maintained by the JF Project (JF@linux.or.jp), at
+     http://www.linux.or.jp/JF/
 
 00-INDEX
 	- this file.
@@ -20,35 +20,24 @@ BUG-HUNTING
 Changes
 	- list of changes that break older software packages.
 CodingStyle
-	- how the maintainers expect the C code in the kernel to look.
+	- how the boss likes the C code in the kernel to look.
+development-process/
+	- An extended tutorial on how to work with the kernel development
+	  process.
 DMA-API.txt
 	- DMA API, pci_ API & extensions for non-consistent memory machines.
-DMA-API-HOWTO.txt
-	- Dynamic DMA mapping Guide
 DMA-ISA-LPC.txt
 	- How to do DMA with ISA (and LPC) devices.
-DMA-attributes.txt
-	- listing of the various possible attributes a DMA region can have
-dmatest.txt
-	- how to compile, configure and use the dmatest system.
 DocBook/
 	- directory with DocBook templates etc. for kernel documentation.
-EDID/
-	- directory with info on customizing EDID for broken gfx/displays.
 HOWTO
 	- the process and procedures of how to do Linux kernel development.
 IPMI.txt
 	- info on Linux Intelligent Platform Management Interface (IPMI) Driver.
 IRQ-affinity.txt
 	- how to select which CPU(s) handle which interrupt events on SMP.
-IRQ-domain.txt
-	- info on interrupt numbering and setting up IRQ domains.
 IRQ.txt
 	- description of what an IRQ is.
-Intel-IOMMU.txt
-	- basic info on the Intel IOMMU virtualization support.
-Makefile
-	- some files in Documentation dir are actually sample code to build
 ManagementStyle
 	- how to (attempt to) manage kernel hackers.
 RCU/
@@ -77,22 +66,12 @@ applying-patches.txt
 	- description of various trees and how to apply their patches.
 arm/
 	- directory with info about Linux on the ARM architecture.
-arm64/
-	- directory with info about Linux on the 64 bit ARM architecture.
-assoc_array.txt
-	- generic associative array intro.
 atomic_ops.txt
 	- semantics and behavior of atomic and bitmask operations.
 auxdisplay/
 	- misc. LCD driver documentation (cfag12864b, ks0108).
-backlight/
-	- directory with info on controlling backlights in flat panel displays
-bad_memory.txt
-	- how to use kernel parameters to exclude bad RAM regions.
 basic_profiling.txt
 	- basic instructions for those who wants to profile Linux kernel.
-bcache.txt
-	- Block-layer cache on fast SSDs to improve slow (raid) I/O performance.
 binfmt_misc.txt
 	- info on the kernel support for extra binary formats.
 blackfin/
@@ -101,14 +80,8 @@ block/
 	- info on the Block I/O (BIO) layer.
 blockdev/
 	- info on block devices & drivers
-braille-console.txt
-	- info on how to use serial devices for Braille support.
-bt8xxgpio.txt
-	- info on how to modify a bt8xx video card for GPIO usage.
 btmrvl.txt
 	- info on Marvell Bluetooth driver usage.
-bus-devices/
-	- directory with info on TI GPMC (General Purpose Memory Controller)
 bus-virt-phys-mapping.txt
 	- how to access I/O mapped memory from within device drivers.
 cachetlb.txt
@@ -117,12 +90,6 @@ cdrom/
 	- directory with information on the CD-ROM drivers that Linux has.
 cgroups/
 	- cgroups features, including cpusets and memory controller.
-circular-buffers.txt
-	- how to make use of the existing circular buffer infrastructure
-clk.txt
-	- info on the common clock framework
-coccinelle.txt
-	- info on how to get and use the Coccinelle code checking tool.
 connector/
 	- docs on the netlink based userspace<->kernel space communication mod.
 console/
@@ -137,8 +104,6 @@ cpuidle/
 	- info on CPU_IDLE, CPU idle state management subsystem.
 cputopology.txt
 	- documentation on how CPU topology info is exported via sysfs.
-crc32.txt
-	- brief tutorial on CRC computation
 cris/
 	- directory with info about Linux on CRIS architecture.
 crypto/
@@ -147,70 +112,40 @@ dcdbas.txt
 	- information on the Dell Systems Management Base Driver.
 debugging-modules.txt
 	- some notes on debugging modules after Linux 2.6.3.
-debugging-via-ohci1394.txt
-	- how to use firewire like a hardware debugger memory reader.
 dell_rbu.txt
 	- document demonstrating the use of the Dell Remote BIOS Update driver.
-development-process/
-	- how to work with the mainline kernel development process.
 device-mapper/
 	- directory with info on Device Mapper.
 devices.txt
 	- plain ASCII listing of all the nodes in /dev/ with major minor #'s.
-devicetree/
-	- directory with info on device tree files used by OF/PowerPC/ARM
-digsig.txt
-	-info on the Digital Signature Verification API
-dma-buf-sharing.txt
-	- the DMA Buffer Sharing API Guide
-dmaengine.txt
-	-the DMA Engine API Guide
 dontdiff
 	- file containing a list of files that should never be diff'ed.
 driver-model/
 	- directory with info about Linux driver model.
 dvb/
 	- info on Linux Digital Video Broadcast (DVB) subsystem.
-dynamic-debug-howto.txt
-	- how to use the dynamic debug (dyndbg) feature.
 early-userspace/
 	- info about initramfs, klibc, and userspace early during boot.
 edac.txt
 	- information on EDAC - Error Detection And Correction
-efi-stub.txt
-	- How to use the EFI boot stub to bypass GRUB or elilo on EFI systems.
 eisa.txt
 	- info on EISA bus support.
-email-clients.txt
-	- info on how to use e-mail to send un-mangled (git) patches.
-extcon/
-	- directory with porting guide for Android kernel switch driver.
 fault-injection/
 	- dir with docs about the fault injection capabilities infrastructure.
 fb/
 	- directory with info on the frame buffer graphics abstraction layer.
+feature-removal-schedule.txt
+	- list of files and features that are going to be removed.
 filesystems/
 	- info on the vfs and the various filesystems that Linux supports.
 firmware_class/
 	- request_firmware() hotplug interface info.
-flexible-arrays.txt
-	- how to make use of flexible sized arrays in linux
-fmc/
-	- information about the FMC bus abstraction
 frv/
 	- Fujitsu FR-V Linux documentation.
-futex-requeue-pi.txt
-	- info on requeueing of tasks from a non-PI futex to a PI futex
-gcov.txt
-	- use of GCC's coverage testing tool "gcov" with the Linux kernel
-gpio/
-	- gpio related documentation
-hid/
-	- directory with information on human interface devices
+gpio.txt
+	- overview of GPIO (General Purpose Input/Output) access conventions.
 highuid.txt
 	- notes on the change from 16 bit to 32 bit user/group IDs.
-hwspinlock.txt
-	- hardware spinlock provides hardware assistance for synchronization
 timers/
 	- info on the timer related topics
 hw_random.txt
@@ -227,14 +162,10 @@ ia64/
 	- directory with info about Linux on Intel 64 bit architecture.
 infiniband/
 	- directory with documents concerning Linux InfiniBand support.
-init.txt
-	- what to do when the kernel can't find the 1st process to run.
 initrd.txt
 	- how to use the RAM disk as an initial/temporary root filesystem.
 input/
 	- info on Linux input device support.
-intel_txt.txt
-	- info on intel Trusted Execution Technology (intel TXT).
 io-mapping.txt
 	- description of io_mapping functions in linux/io-mapping.h
 io_ordering.txt
@@ -251,8 +182,6 @@ isdn/
 	- directory with info on the Linux ISDN support, and supported cards.
 java.txt
 	- info on the in-kernel binary support for Java(tm).
-ja_JP/
-	- directory with Japanese translations of various documents
 kbuild/
 	- directory with info about the kernel build process.
 kdump/
@@ -263,14 +192,6 @@ kernel-docs.txt
 	- listing of various WWW + books that document kernel internals.
 kernel-parameters.txt
 	- summary listing of command line / boot prompt args for the kernel.
-kernel-per-CPU-kthreads.txt
-	- List of all per-CPU kthreads and how they introduce jitter.
-kmemcheck.txt
-	- info on dynamic checker that detects uses of uninitialized memory.
-kmemleak.txt
-	- info on how to make use of the kernel memory leak detection system
-ko_KR/
-	- directory with Korean translations of various documents
 kobject.txt
 	- info of the kobject infrastructure of the Linux kernel.
 kprobes.txt
@@ -287,12 +208,6 @@ local_ops.txt
 	- semantics and behavior of local atomic operations.
 lockdep-design.txt
 	- documentation on the runtime locking correctness validator.
-locking/
-	- directory with info about kernel locking primitives
-lockstat.txt
-	- info on collecting statistics on locks (and contention).
-lockup-watchdogs.txt
-	- info on soft and hard lockup detectors (aka nmi_watchdog).
 logo.gif
 	- full colour GIF image of Linux logo (penguin - Tux).
 logo.txt
@@ -301,30 +216,20 @@ m68k/
 	- directory with info about Linux on Motorola 68k architecture.
 magic-number.txt
 	- list of magic numbers used to mark/protect kernel data structures.
+mca.txt
+	- info on supporting Micro Channel Architecture (e.g. PS/2) systems.
 md.txt
 	- info on boot arguments for the multiple devices driver.
-media-framework.txt
-	- info on media framework, its data structures, functions and usage.
 memory-barriers.txt
 	- info on Linux kernel memory barriers.
-memory-devices/
-	- directory with info on parts like the Texas Instruments EMIF driver
 memory-hotplug.txt
 	- Hotpluggable memory support, how to use and current status.
-metag/
-	- directory with info about Linux on Meta architecture.
+memory.txt
+	- info on typical Linux memory problems.
 mips/
 	- directory with info about Linux on MIPS architecture.
-misc-devices/
-	- directory with info about devices using the misc dev subsystem
 mmc/
 	- directory with info about the MMC subsystem
-mn10300/
-	- directory with info about the mn10300 architecture port
-module-signing.txt
-	- Kernel module signing for increased security when loading modules.
-mtd/
-	- directory with info about memory technology devices (flash)
 mono.txt
 	- how to execute Mono-based .NET binaries with the help of BINFMT_MISC.
 mutex-design.txt
@@ -335,8 +240,8 @@ netlabel/
 	- directory with information on the NetLabel subsystem.
 networking/
 	- directory with info on various aspects of networking with Linux.
-nfc/
-	- directory relating info about Near Field Communications support.
+nmi_watchdog.txt
+	- info on NMI watchdog for SMP systems.
 nommu-mmap.txt
 	- documentation about no-mmu memory mapping support.
 numastat.txt
@@ -353,48 +258,28 @@ parport-lowlevel.txt
 	- description and usage of the low level parallel port functions.
 pcmcia/
 	- info on the Linux PCMCIA driver.
-percpu-rw-semaphore.txt
-	- RCU based read-write semaphore optimized for locking for reading
-phy.txt
-	- Description of the generic PHY framework.
 pi-futex.txt
-	- documentation on lightweight priority inheritance futexes.
-pinctrl.txt
-	- info on pinctrl subsystem and the PINMUX/PINCONF and drivers
+	- documentation on lightweight PI-futexes.
 pnp.txt
 	- Linux Plug and Play documentation.
 power/
 	- directory with info on Linux PCI power management.
 powerpc/
 	- directory with info on using Linux with the PowerPC.
-prctl/
-	- directory with info on the priveledge control subsystem
 preempt-locking.txt
 	- info on locking under a preemptive kernel.
 printk-formats.txt
 	- how to get printk format specifiers right
-pps/
-	- directory with information on the pulse-per-second support
-ptp/
-	- directory with info on support for IEEE 1588 PTP clocks in Linux.
-pwm.txt
-	- info on the pulse width modulation driver subsystem
+prio_tree.txt
+	- info on radix-priority-search-tree use for indexing vmas.
 ramoops.txt
 	- documentation of the ramoops oops/panic logging module.
-rapidio/
-	- directory with info on RapidIO packet-based fabric interconnect
 rbtree.txt
 	- info on what red-black trees are and what they are for.
-remoteproc.txt
-	- info on how to handle remote processor (e.g. AMP) offloads/usage.
-rfkill.txt
-	- info on the radio frequency kill switch subsystem/support.
 robust-futex-ABI.txt
 	- documentation of the robust futex ABI.
 robust-futexes.txt
 	- a description of what robust futexes are.
-rpmsg.txt
-	- info on the Remote Processor Messaging (rpmsg) Framework
 rt-mutex-design.txt
 	- description of the RealTime mutex implementation design.
 rt-mutex.txt
@@ -415,12 +300,14 @@ serial-console.txt
 	- how to set up Linux with a serial line console as the default.
 sgi-ioc4.txt
 	- description of the SGI IOC4 PCI (multi function) device.
+sgi-visws.txt
+	- short blurb on the SGI Visual Workstations.
 sh/
 	- directory with info on porting Linux to a new architecture.
-smsc_ece1099.txt
-	-info on the smsc Keyboard Scan Expansion/GPIO Expansion device.
 sound/
 	- directory with info on sound card support.
+sparc/
+	- directory with info on using Linux on Sparc architecture.
 sparse.txt
 	- info on how to obtain and use the sparse tool for typechecking.
 spi/
@@ -431,8 +318,6 @@ stable_api_nonsense.txt
 	- info on why the kernel does not have a stable in-kernel api or abi.
 stable_kernel_rules.txt
 	- rules and procedures for the -stable kernel releases.
-static-keys.txt
-	- info on how static keys allow debug code in hotpaths via patching
 svga.txt
 	- short guide on selecting video modes at boot via VGA BIOS.
 sysfs-rules.txt
@@ -441,57 +326,27 @@ sysctl/
 	- directory with info on the /proc/sys/* files.
 sysrq.txt
 	- info on the magic SysRq key.
-target/
-	- directory with info on generating TCM v4 fabric .ko modules
-this_cpu_ops.txt
-	- List rationale behind and the way to use this_cpu operations.
-thermal/
-	- directory with information on managing thermal issues (CPU/temp)
-trace/
-	- directory with info on tracing technologies within linux
-unaligned-memory-access.txt
-	- info on how to avoid arch breaking unaligned memory access in code.
+telephony/
+	- directory with info on telephony (e.g. voice over IP) support.
 unicode.txt
 	- info on the Unicode character/font mapping used in Linux.
 unshare.txt
 	- description of the Linux unshare system call.
 usb/
 	- directory with info regarding the Universal Serial Bus.
-vDSO/
-	- directory with info regarding virtual dynamic shared objects
-vfio.txt
-	- info on Virtual Function I/O used in guest/hypervisor instances.
-vgaarbiter.txt
-	- info on enable/disable the legacy decoding on different VGA devices
 video-output.txt
 	- sysfs class driver interface to enable/disable a video output device.
 video4linux/
 	- directory with info regarding video/TV/radio cards and linux.
-virtual/
-	- directory with information on the various linux virtualizations.
 vm/
 	- directory with info on the Linux vm code.
-vme_api.txt
-	- file relating info on the VME bus API in linux
 volatile-considered-harmful.txt
 	- Why the "volatile" type class should not be used
 w1/
 	- directory with documents regarding the 1-wire (w1) subsystem.
 watchdog/
 	- how to auto-reboot Linux if it has "fallen and can't get up". ;-)
-wimax/
-	- directory with info about Intel Wireless Wimax Connections
-workqueue.txt
-	- information on the Concurrency Managed Workqueue implementation
-ww-mutex-design.txt
-	- Intro to Mutex wait/would deadlock handling.s
 x86/x86_64/
 	- directory with info on Linux support for AMD x86-64 (Hammer) machines.
-xtensa/
-	- directory with documents relating to arch/xtensa port/implementation
-xz.txt
-	- how to make use of the XZ data compression within linux kernel
-zh_CN/
-	- directory with Chinese translations of various documents
 zorro.txt
 	- info on writing drivers for Zorro bus devices found on Amigas.

Documentation/ABI/README

@@ -36,6 +36,9 @@ The different levels of stability are:
 	the kernel, but are marked to be removed at some later point in
 	time.  The description of the interface will document the reason
 	why it is obsolete and when it can be expected to be removed.
+	The file Documentation/feature-removal-schedule.txt may describe
+	some of these interfaces, giving a schedule for when they will
+	be removed.
 
   removed/
 	This directory contains a list of the old interfaces that have
@@ -72,16 +75,3 @@ kernel tree without going through the obsolete state first.
 
 It's up to the developer to place their interfaces in the category they
 wish for it to start out in.
-
-
-Notable bits of non-ABI, which should not under any circumstances be considered
-stable:
-
-- Kconfig.  Userspace should not rely on the presence or absence of any
-  particular Kconfig symbol, in /proc/config.gz, in the copy of .config
-  commonly installed to /boot, or in any invocation of the kernel build
-  process.
-
-- Kernel-internal symbols.  Do not rely on the presence, absence, location, or
-  type of any kernel symbol, either in System.map files or the kernel binary
-  itself.  See Documentation/stable_api_nonsense.txt.

Documentation/ABI/obsolete/proc-pid-oom_adj

@@ -0,0 +1,22 @@
+What:	/proc/<pid>/oom_adj
+When:	August 2012
+Why:	/proc/<pid>/oom_adj allows userspace to influence the oom killer's
+	badness heuristic used to determine which task to kill when the kernel
+	is out of memory.
+
+	The badness heuristic has since been rewritten since the introduction of
+	this tunable such that its meaning is deprecated.  The value was
+	implemented as a bitshift on a score generated by the badness()
+	function that did not have any precise units of measure.  With the
+	rewrite, the score is given as a proportion of available memory to the
+	task allocating pages, so using a bitshift which grows the score
+	exponentially is, thus, impossible to tune with fine granularity.
+
+	A much more powerful interface, /proc/<pid>/oom_score_adj, was
+	introduced with the oom killer rewrite that allows users to increase or
+	decrease the badness score linearly.  This interface will replace
+	/proc/<pid>/oom_adj.
+
+	A warning will be emitted to the kernel log if an application uses this
+	deprecated interface.  After it is printed once, future warnings will be
+	suppressed until the kernel is rebooted.

Documentation/ABI/obsolete/proc-sys-vm-nr_pdflush_threads

@@ -1,5 +0,0 @@
-What:		/proc/sys/vm/nr_pdflush_threads
-Date:		June 2012
-Contact:	Wanpeng Li <liwp@linux.vnet.ibm.com>
-Description: Since pdflush is replaced by per-BDI flusher, the interface of old pdflush
-             exported in /proc/sys/vm/ should be removed.

Documentation/ABI/obsolete/sysfs-class-rfkill

@@ -7,7 +7,7 @@ Date:		09-Jul-2007
 KernelVersion	v2.6.22
 Contact:	linux-wireless@vger.kernel.org
 Description: 	Current state of the transmitter.
-		This file is deprecated and scheduled to be removed in 2014,
+		This file is deprecated and sheduled to be removed in 2014,
 		because its not possible to express the 'soft and hard block'
 		state of the rfkill driver.
 Values: 	A numeric value.

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-koneplus

@@ -8,41 +8,3 @@ Description:	The integer value of this attribute ranges from 0-4.
 		When written, this file sets the number of the startup profile
 		and the mouse activates this profile immediately.
 		Please use actual_profile, it does the same thing.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/firmware_version
-Date:		October 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	When read, this file returns the raw integer version number of the
-		firmware reported by the mouse. Using the integer value eases
-		further usage in other programs. To receive the real version
-		number the decimal point has to be shifted 2 positions to the
-		left. E.g. a returned value of 121 means 1.21
-		This file is readonly.
-		Please read binary attribute info which contains firmware version.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_buttons
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The mouse can store 5 profiles which can be switched by the
-		press of a button. A profile is split in settings and buttons.
-		profile_buttons holds information about button layout.
-		When read, these files return the respective profile buttons.
-		The returned data is 77 bytes in size.
-		This file is readonly.
-		Write control to select profile and read profile_buttons instead.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/koneplus/roccatkoneplus<minor>/profile[1-5]_settings
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The mouse can store 5 profiles which can be switched by the
-		press of a button. A profile is split in settings and buttons.
-		profile_settings holds information like resolution, sensitivity
-		and light effects.
-		When read, these files return the respective profile settings.
-		The returned data is 43 bytes in size.
-		This file is readonly.
-		Write control to select profile and read profile_settings instead.
-Users:		http://roccat.sourceforge.net

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-kovaplus

@@ -1,66 +0,0 @@
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_cpi
-Date:		January 2011
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The integer value of this attribute ranges from 1-4.
-		When read, this attribute returns the number of the active
-		cpi level.
-		This file is readonly.
-		Has never been used. If bookkeeping is done, it's done in userland tools.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_x
-Date:		January 2011
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The integer value of this attribute ranges from 1-10.
-		When read, this attribute returns the number of the actual
-		sensitivity in x direction.
-		This file is readonly.
-		Has never been used. If bookkeeping is done, it's done in userland tools.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/actual_sensitivity_y
-Date:		January 2011
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The integer value of this attribute ranges from 1-10.
-		When read, this attribute returns the number of the actual
-		sensitivity in y direction.
-		This file is readonly.
-		Has never been used. If bookkeeping is done, it's done in userland tools.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/firmware_version
-Date:		January 2011
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	When read, this file returns the raw integer version number of the
-		firmware reported by the mouse. Using the integer value eases
-		further usage in other programs. To receive the real version
-		number the decimal point has to be shifted 2 positions to the
-		left. E.g. a returned value of 121 means 1.21
-		This file is readonly.
-		Obsoleted by binary sysfs attribute "info".
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_buttons
-Date:		January 2011
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The mouse can store 5 profiles which can be switched by the
-		press of a button. A profile is split in settings and buttons.
-		profile_buttons holds information about button layout.
-		When read, these files return the respective profile buttons.
-		The returned data is 23 bytes in size.
-		This file is readonly.
-		Write control to select profile and read profile_buttons instead.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/kovaplus/roccatkovaplus<minor>/profile[1-5]_settings
-Date:		January 2011
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The mouse can store 5 profiles which can be switched by the
-		press of a button. A profile is split in settings and buttons.
-		profile_settings holds information like resolution, sensitivity
-		and light effects.
-		When read, these files return the respective profile settings.
-		The returned data is 16 bytes in size.
-		This file is readonly.
-		Write control to select profile and read profile_settings instead.
-Users:		http://roccat.sourceforge.net

Documentation/ABI/obsolete/sysfs-driver-hid-roccat-pyra

@@ -1,73 +0,0 @@
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_cpi
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	It is possible to switch the cpi setting of the mouse with the
-		press of a button.
-		When read, this file returns the raw number of the actual cpi
-		setting reported by the mouse. This number has to be further
-		processed to receive the real dpi value.
-
-		VALUE DPI
-		1     400
-		2     800
-		4     1600
-
-		This file is readonly.
-		Has never been used. If bookkeeping is done, it's done in userland tools.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/actual_profile
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	When read, this file returns the number of the actual profile in
-		range 0-4.
-		This file is readonly.
-		Please use binary attribute "settings" which provides this information.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/firmware_version
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	When read, this file returns the raw integer version number of the
-		firmware reported by the mouse. Using the integer value eases
-		further usage in other programs. To receive the real version
-		number the decimal point has to be shifted 2 positions to the
-		left. E.g. a returned value of 138 means 1.38
-		This file is readonly.
-		Please use binary attribute "info" which provides this information.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_buttons
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The mouse can store 5 profiles which can be switched by the
-		press of a button. A profile is split in settings and buttons.
-		profile_buttons holds information about button layout.
-		When read, these files return the respective profile buttons.
-		The returned data is 19 bytes in size.
-		This file is readonly.
-		Write control to select profile and read profile_buttons instead.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/profile[1-5]_settings
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The mouse can store 5 profiles which can be switched by the
-		press of a button. A profile is split in settings and buttons.
-		profile_settings holds information like resolution, sensitivity
-		and light effects.
-		When read, these files return the respective profile settings.
-		The returned data is 13 bytes in size.
-		This file is readonly.
-		Write control to select profile and read profile_settings instead.
-Users:		http://roccat.sourceforge.net
-
-What:		/sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<product-id>.<num>/pyra/roccatpyra<minor>/startup_profile
-Date:		August 2010
-Contact:	Stefan Achatz <erazor_de@users.sourceforge.net>
-Description:	The integer value of this attribute ranges from 0-4.
-                When read, this attribute returns the number of the profile
-                that's active when the mouse is powered on.
-		This file is readonly.
-		Please use binary attribute "settings" which provides this information.
-Users:		http://roccat.sourceforge.net

Documentation/ABI/removed/devfs

@@ -1,6 +1,6 @@
 What:		devfs
 Date:		July 2005 (scheduled), finally removed in kernel v2.6.18
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
 	devfs has been unmaintained for a number of years, has unfixable
 	races, contains a naming policy within the kernel that is

Documentation/ABI/removed/ip_queue

@@ -1,9 +0,0 @@
-What:		ip_queue
-Date:		finally removed in kernel v3.5.0
-Contact:	Pablo Neira Ayuso <pablo@netfilter.org>
-Description:
-	ip_queue has been replaced by nfnetlink_queue which provides
-	more advanced queueing mechanism to user-space. The ip_queue
-	module was already announced to become obsolete years ago.
-
-Users:

Documentation/ABI/removed/net_dma

@@ -1,8 +0,0 @@
-What:		tcp_dma_copybreak sysctl
-Date:		Removed in kernel v3.13
-Contact:	Dan Williams <dan.j.williams@intel.com>
-Description:
-	Formerly the lower limit, in bytes, of the size of socket reads
-	that will be offloaded to a DMA copy engine.  Removed due to
-	coherency issues of the cpu potentially touching the buffers
-	while dma is in flight.

Documentation/ABI/stable/sysfs-bus-firewire

@@ -39,17 +39,6 @@ Users:		udev rules to set ownership and access permissions or ACLs of
 		/dev/fw[0-9]+ character device files
 
 
-What:		/sys/bus/firewire/devices/fw[0-9]+/is_local
-Date:		July 2012
-KernelVersion:	3.6
-Contact:	linux1394-devel@lists.sourceforge.net
-Description:
-		IEEE 1394 node device attribute.
-		Read-only and immutable.
-Values:		1: The sysfs entry represents a local node (a controller card).
-		0: The sysfs entry represents a remote node.
-
-
 What:		/sys/bus/firewire/devices/fw[0-9]+[.][0-9]+/
 Date:		May 2007
 KernelVersion:	2.6.22

Documentation/ABI/stable/sysfs-bus-usb

@@ -1,142 +0,0 @@
-What:		/sys/bus/usb/devices/.../power/persist
-Date:		May 2007
-KernelVersion:	2.6.23
-Contact:	Alan Stern <stern@rowland.harvard.edu>
-Description:
-		USB device directories can contain a file named power/persist.
-		The file holds a boolean value (0 or 1) indicating whether or
-		not the "USB-Persist" facility is enabled for the device.  For
-		hubs this facility is always enabled and their device
-		directories will not contain this file.
-
-		For more information, see Documentation/usb/persist.txt.
-
-What:		/sys/bus/usb/devices/.../power/autosuspend
-Date:		March 2007
-KernelVersion:	2.6.21
-Contact:	Alan Stern <stern@rowland.harvard.edu>
-Description:
-		Each USB device directory will contain a file named
-		power/autosuspend.  This file holds the time (in seconds)
-		the device must be idle before it will be autosuspended.
-		0 means the device will be autosuspended as soon as
-		possible.  Negative values will prevent the device from
-		being autosuspended at all, and writing a negative value
-		will resume the device if it is already suspended.
-
-		The autosuspend delay for newly-created devices is set to
-		the value of the usbcore.autosuspend module parameter.
-
-What:		/sys/bus/usb/device/.../power/connected_duration
-Date:		January 2008
-KernelVersion:	2.6.25
-Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
-Description:
-		If CONFIG_PM_RUNTIME is enabled then this file
-		is present.  When read, it returns the total time (in msec)
-		that the USB device has been connected to the machine.  This
-		file is read-only.
-Users:
-		PowerTOP <powertop@lists.01.org>
-		https://01.org/powertop/
-
-What:		/sys/bus/usb/device/.../power/active_duration
-Date:		January 2008
-KernelVersion:	2.6.25
-Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
-Description:
-		If CONFIG_PM_RUNTIME is enabled then this file
-		is present.  When read, it returns the total time (in msec)
-		that the USB device has been active, i.e. not in a suspended
-		state.  This file is read-only.
-
-		Tools can use this file and the connected_duration file to
-		compute the percentage of time that a device has been active.
-		For example,
-		echo $((100 * `cat active_duration` / `cat connected_duration`))
-		will give an integer percentage.  Note that this does not
-		account for counter wrap.
-Users:
-		PowerTOP <powertop@lists.01.org>
-		https://01.org/powertop/
-
-What:		/sys/bus/usb/devices/<busnum>-<port[.port]>...:<config num>-<interface num>/supports_autosuspend
-Date:		January 2008
-KernelVersion:	2.6.27
-Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
-Description:
-		When read, this file returns 1 if the interface driver
-		for this interface supports autosuspend.  It also
-		returns 1 if no driver has claimed this interface, as an
-		unclaimed interface will not stop the device from being
-		autosuspended if all other interface drivers are idle.
-		The file returns 0 if autosuspend support has not been
-		added to the driver.
-Users:
-		USB PM tool
-		git://git.moblin.org/users/sarah/usb-pm-tool/
-
-What:		/sys/bus/usb/device/.../avoid_reset_quirk
-Date:		December 2009
-Contact:	Oliver Neukum <oliver@neukum.org>
-Description:
-		Writing 1 to this file tells the kernel that this
-		device will morph into another mode when it is reset.
-		Drivers will not use reset for error handling for
-		such devices.
-Users:
-		usb_modeswitch
-
-What:		/sys/bus/usb/devices/.../devnum
-KernelVersion:	since at least 2.6.18
-Description:
-		Device address on the USB bus.
-Users:
-		libusb
-
-What:		/sys/bus/usb/devices/.../bConfigurationValue
-KernelVersion:	since at least 2.6.18
-Description:
-		bConfigurationValue of the *active* configuration for the
-		device. Writing 0 or -1 to bConfigurationValue will reset the
-		active configuration (unconfigure the device). Writing
-		another value will change the active configuration.
-
-		Note that some devices, in violation of the USB spec, have a
-		configuration with a value equal to 0. Writing 0 to
-		bConfigurationValue for these devices will install that
-		configuration, rather then unconfigure the device.
-
-		Writing -1 will always unconfigure the device.
-Users:
-		libusb
-
-What:		/sys/bus/usb/devices/.../busnum
-KernelVersion:	2.6.22
-Description:
-		Bus-number of the USB-bus the device is connected to.
-Users:
-		libusb
-
-What:		/sys/bus/usb/devices/.../descriptors
-KernelVersion:	2.6.26
-Description:
-		Binary file containing cached descriptors of the device. The
-		binary data consists of the device descriptor followed by the
-		descriptors for each configuration of the device.
-		Note that the wTotalLength of the config descriptors can not
-		be trusted, as the device may have a smaller config descriptor
-		than it advertises. The bLength field of each (sub) descriptor
-		can be trusted, and can be used to seek forward one (sub)
-		descriptor at a time until the next config descriptor is found.
-		All descriptors read from this file are in bus-endian format
-Users:
-		libusb
-
-What:		/sys/bus/usb/devices/.../speed
-KernelVersion:	since at least 2.6.18
-Description:
-		Speed the device is connected with to the usb-host in
-		Mbit / second. IE one of 1.5 / 12 / 480 / 5000.
-Users:
-		libusb

Documentation/ABI/stable/sysfs-bus-xen-backend

@@ -1,75 +0,0 @@
-What:		/sys/bus/xen-backend/devices/*/devtype
-Date:		Feb 2009
-KernelVersion:	2.6.38
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                The type of the device.  e.g., one of: 'vbd' (block),
-                'vif' (network), or 'vfb' (framebuffer).
-
-What:		/sys/bus/xen-backend/devices/*/nodename
-Date:		Feb 2009
-KernelVersion:	2.6.38
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                XenStore node (under /local/domain/NNN/) for this
-                backend device.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/physical_device
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                The major:minor number (in hexidecimal) of the
-                physical device providing the storage for this backend
-                block device.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/mode
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Whether the block device is read-only ('r') or
-                read-write ('w').
-
-What:		/sys/bus/xen-backend/devices/vbd-*/statistics/f_req
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Number of flush requests from the frontend.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/statistics/oo_req
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Number of requests delayed because the backend was too
-                busy processing previous requests.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/statistics/rd_req
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Number of read requests from the frontend.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/statistics/rd_sect
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Number of sectors read by the frontend.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/statistics/wr_req
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Number of write requests from the frontend.
-
-What:		/sys/bus/xen-backend/devices/vbd-*/statistics/wr_sect
-Date:		April 2011
-KernelVersion:	3.0
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-                Number of sectors written by the frontend.

Documentation/ABI/stable/sysfs-class-tpm

@@ -1,185 +0,0 @@
-What:		/sys/class/misc/tpmX/device/
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The device/ directory under a specific TPM instance exposes
-		the properties of that TPM chip
-
-
-What:		/sys/class/misc/tpmX/device/active
-Date:		April 2006
-KernelVersion:	2.6.17
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "active" property prints a '1' if the TPM chip is accepting
-		commands. An inactive TPM chip still contains all the state of
-		an active chip (Storage Root Key, NVRAM, etc), and can be
-		visible to the OS, but will only accept a restricted set of
-		commands. See the TPM Main Specification part 2, Structures,
-		section 17 for more information on which commands are
-		available.
-
-What:		/sys/class/misc/tpmX/device/cancel
-Date:		June 2005
-KernelVersion:	2.6.13
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "cancel" property allows you to cancel the currently
-		pending TPM command. Writing any value to cancel will call the
-		TPM vendor specific cancel operation.
-
-What:		/sys/class/misc/tpmX/device/caps
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "caps" property contains TPM manufacturer and version info.
-
-		Example output:
-
-		Manufacturer: 0x53544d20
-		TCG version: 1.2
-		Firmware version: 8.16
-
-		Manufacturer is a hex dump of the 4 byte manufacturer info
-		space in a TPM. TCG version shows the TCG TPM spec level that
-		the chip supports. Firmware version is that of the chip and
-		is manufacturer specific.
-
-What:		/sys/class/misc/tpmX/device/durations
-Date:		March 2011
-KernelVersion:	3.1
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "durations" property shows the 3 vendor-specific values
-		used to wait for a short, medium and long TPM command. All
-		TPM commands are categorized as short, medium or long in
-		execution time, so that the driver doesn't have to wait
-		any longer than necessary before starting to poll for a
-		result.
-
-		Example output:
-
-		3015000 4508000 180995000 [original]
-
-		Here the short, medium and long durations are displayed in
-		usecs. "[original]" indicates that the values are displayed
-		unmodified from when they were queried from the chip.
-		Durations can be modified in the case where a buggy chip
-		reports them in msec instead of usec and they need to be
-		scaled to be displayed in usecs. In this case "[adjusted]"
-		will be displayed in place of "[original]".
-
-What:		/sys/class/misc/tpmX/device/enabled
-Date:		April 2006
-KernelVersion:	2.6.17
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "enabled" property prints a '1' if the TPM chip is enabled,
-		meaning that it should be visible to the OS. This property
-		may be visible but produce a '0' after some operation that
-		disables the TPM.
-
-What:		/sys/class/misc/tpmX/device/owned
-Date:		April 2006
-KernelVersion:	2.6.17
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "owned" property produces a '1' if the TPM_TakeOwnership
-		ordinal has been executed successfully in the chip. A '0'
-		indicates that ownership hasn't been taken.
-
-What:		/sys/class/misc/tpmX/device/pcrs
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "pcrs" property will dump the current value of all Platform
-		Configuration Registers in the TPM. Note that since these
-		values may be constantly changing, the output is only valid
-		for a snapshot in time.
-
-		Example output:
-
-		PCR-00: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
-		PCR-01: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
-		PCR-02: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
-		PCR-03: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
-		PCR-04: 3A 3F 78 0F 11 A4 B4 99 69 FC AA 80 CD 6E 39 57 C3 3B 22 75
-		...
-
-		The number of PCRs and hex bytes needed to represent a PCR
-		value will vary depending on TPM chip version. For TPM 1.1 and
-		1.2 chips, PCRs represent SHA-1 hashes, which are 20 bytes
-		long. Use the "caps" property to determine TPM version.
-
-What:		/sys/class/misc/tpmX/device/pubek
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "pubek" property will return the TPM's public endorsement
-		key if possible. If the TPM has had ownership established and
-		is version 1.2, the pubek will not be available without the
-		owner's authorization. Since the TPM driver doesn't store any
-		secrets, it can't authorize its own request for the pubek,
-		making it unaccessible. The public endorsement key is gener-
-		ated at TPM menufacture time and exists for the life of the
-		chip.
-
-		Example output:
-
-		Algorithm: 00 00 00 01
-		Encscheme: 00 03
-		Sigscheme: 00 01
-		Parameters: 00 00 08 00 00 00 00 02 00 00 00 00
-		Modulus length: 256
-		Modulus:
-		B4 76 41 82 C9 20 2C 10 18 40 BC 8B E5 44 4C 6C
-		3A B2 92 0C A4 9B 2A 83 EB 5C 12 85 04 48 A0 B6
-		1E E4 81 84 CE B2 F2 45 1C F0 85 99 61 02 4D EB
-		86 C4 F7 F3 29 60 52 93 6B B2 E5 AB 8B A9 09 E3
-		D7 0E 7D CA 41 BF 43 07 65 86 3C 8C 13 7A D0 8B
-		82 5E 96 0B F8 1F 5F 34 06 DA A2 52 C1 A9 D5 26
-		0F F4 04 4B D9 3F 2D F2 AC 2F 74 64 1F 8B CD 3E
-		1E 30 38 6C 70 63 69 AB E2 50 DF 49 05 2E E1 8D
-		6F 78 44 DA 57 43 69 EE 76 6C 38 8A E9 8E A3 F0
-		A7 1F 3C A8 D0 12 15 3E CA 0E BD FA 24 CD 33 C6
-		47 AE A4 18 83 8E 22 39 75 93 86 E6 FD 66 48 B6
-		10 AD 94 14 65 F9 6A 17 78 BD 16 53 84 30 BF 70
-		E0 DC 65 FD 3C C6 B0 1E BF B9 C1 B5 6C EF B1 3A
-		F8 28 05 83 62 26 11 DC B4 6B 5A 97 FF 32 26 B6
-		F7 02 71 CF 15 AE 16 DD D1 C1 8E A8 CF 9B 50 7B
-		C3 91 FF 44 1E CF 7C 39 FE 17 77 21 20 BD CE 9B
-
-		Possible values:
-
-		Algorithm:	TPM_ALG_RSA			(1)
-		Encscheme:	TPM_ES_RSAESPKCSv15		(2)
-				TPM_ES_RSAESOAEP_SHA1_MGF1	(3)
-		Sigscheme:	TPM_SS_NONE			(1)
-		Parameters, a byte string of 3 u32 values:
-			Key Length (bits):	00 00 08 00	(2048)
-			Num primes:		00 00 00 02	(2)
-			Exponent Size:		00 00 00 00	(0 means the
-								 default exp)
-		Modulus Length: 256 (bytes)
-		Modulus:	The 256 byte Endorsement Key modulus
-
-What:		/sys/class/misc/tpmX/device/temp_deactivated
-Date:		April 2006
-KernelVersion:	2.6.17
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "temp_deactivated" property returns a '1' if the chip has
-		been temporarily dectivated, usually until the next power
-		cycle. Whether a warm boot (reboot) will clear a TPM chip
-		from a temp_deactivated state is platform specific.
-
-What:		/sys/class/misc/tpmX/device/timeouts
-Date:		March 2011
-KernelVersion:	3.1
-Contact:	tpmdd-devel@lists.sf.net
-Description:	The "timeouts" property shows the 4 vendor-specific values
-		for the TPM's interface spec timeouts. The use of these
-		timeouts is defined by the TPM interface spec that the chip
-		conforms to.
-
-		Example output:
-
-		750000 750000 750000 750000 [original]
-
-		The four timeout values are shown in usecs, with a trailing
-		"[original]" or "[adjusted]" depending on whether the values
-		were scaled by the driver to be reported in usec from msecs.

Documentation/ABI/stable/sysfs-devices-node

@@ -1,93 +1,7 @@
-What:		/sys/devices/system/node/possible
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Nodes that could be possibly become online at some point.
-
-What:		/sys/devices/system/node/online
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Nodes that are online.
-
-What:		/sys/devices/system/node/has_normal_memory
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Nodes that have regular memory.
-
-What:		/sys/devices/system/node/has_cpu
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Nodes that have one or more CPUs.
-
-What:		/sys/devices/system/node/has_high_memory
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Nodes that have regular or high memory.
-		Depends on CONFIG_HIGHMEM.
-
 What:		/sys/devices/system/node/nodeX
 Date:		October 2002
 Contact:	Linux Memory Management list <linux-mm@kvack.org>
 Description:
 		When CONFIG_NUMA is enabled, this is a directory containing
 		information on node X such as what CPUs are local to the
-		node. Each file is detailed next.
-
-What:		/sys/devices/system/node/nodeX/cpumap
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		The node's cpumap.
-
-What:		/sys/devices/system/node/nodeX/cpulist
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		The CPUs associated to the node.
-
-What:		/sys/devices/system/node/nodeX/meminfo
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Provides information about the node's distribution and memory
-		utilization. Similar to /proc/meminfo, see Documentation/filesystems/proc.txt
-
-What:		/sys/devices/system/node/nodeX/numastat
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		The node's hit/miss statistics, in units of pages.
-		See Documentation/numastat.txt
-
-What:		/sys/devices/system/node/nodeX/distance
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		Distance between the node and all the other nodes
-		in the system.
-
-What:		/sys/devices/system/node/nodeX/vmstat
-Date:		October 2002
-Contact:	Linux Memory Management list <linux-mm@kvack.org>
-Description:
-		The node's zoned virtual memory statistics.
-		This is a superset of numastat.
-
-What:		/sys/devices/system/node/nodeX/compact
-Date:		February 2010
-Contact:	Mel Gorman <mel@csn.ul.ie>
-Description:
-		When this file is written to, all memory within that node
-		will be compacted. When it completes, memory will be freed
-		into blocks which have as many contiguous pages as possible
-
-What:		/sys/devices/system/node/nodeX/hugepages/hugepages-<size>/
-Date:		December 2009
-Contact:	Lee Schermerhorn <lee.schermerhorn@hp.com>
-Description:
-		The node's huge page size control/query attributes.
-		See Documentation/vm/hugetlbpage.txt
+		node.

Documentation/ABI/stable/sysfs-devices-system-cpu

@@ -1,25 +0,0 @@
-What: 		/sys/devices/system/cpu/dscr_default
-Date:		13-May-2014
-KernelVersion:	v3.15.0
-Contact:
-Description:	Writes are equivalent to writing to
-		/sys/devices/system/cpu/cpuN/dscr on all CPUs.
-		Reads return the last written value or 0.
-		This value is not a global default: it is a way to set
-		all per-CPU defaults at the same time.
-Values:		64 bit unsigned integer (bit field)
-
-What: 		/sys/devices/system/cpu/cpu[0-9]+/dscr
-Date:		13-May-2014
-KernelVersion:	v3.15.0
-Contact:
-Description:	Default value for the Data Stream Control Register (DSCR) on
-		a CPU.
-		This default value is used when the kernel is executing and
-		for any process that has not set the DSCR itself.
-		If a process ever sets the DSCR (via direct access to the
-		SPR) that value will be persisted for that process and used
-		on any CPU where it executes (overriding the value described
-		here).
-		If set by a process it will be inherited by child processes.
-Values:		64 bit unsigned integer (bit field)

Documentation/ABI/stable/sysfs-devices-system-xen_memory

@@ -1,77 +0,0 @@
-What:		/sys/devices/system/xen_memory/xen_memory0/max_retry_count
-Date:		May 2011
-KernelVersion:	2.6.39
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		The maximum number of times the balloon driver will
-		attempt to increase the balloon before giving up.  See
-		also 'retry_count' below.
-		A value of zero means retry forever and is the default one.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/max_schedule_delay
-Date:		May 2011
-KernelVersion:	2.6.39
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		The limit that 'schedule_delay' (see below) will be
-		increased to. The default value is 32 seconds.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/retry_count
-Date:		May 2011
-KernelVersion:	2.6.39
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		The current number of times that the balloon driver
-		has attempted to increase the size of the balloon.
-		The default value is one. With max_retry_count being
-		zero (unlimited), this means that the driver will attempt
-		to retry with a 'schedule_delay' delay.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/schedule_delay
-Date:		May 2011
-KernelVersion:	2.6.39
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		The time (in seconds) to wait between attempts to
-		increase the balloon.  Each time the balloon cannot be
-		increased, 'schedule_delay' is increased (until
-		'max_schedule_delay' is reached at which point it
-		will use the max value).
-
-What:		/sys/devices/system/xen_memory/xen_memory0/target
-Date:		April 2008
-KernelVersion:	2.6.26
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		The target number of pages to adjust this domain's
-		memory reservation to.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/target_kb
-Date:		April 2008
-KernelVersion:	2.6.26
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		As target above, except the value is in KiB.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/info/current_kb
-Date:		April 2008
-KernelVersion:	2.6.26
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		Current size (in KiB) of this domain's memory
-		reservation.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/info/high_kb
-Date:		April 2008
-KernelVersion:	2.6.26
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		Amount (in KiB) of high memory in the balloon.
-
-What:		/sys/devices/system/xen_memory/xen_memory0/info/low_kb
-Date:		April 2008
-KernelVersion:	2.6.26
-Contact:	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
-Description:
-		Amount (in KiB) of low (or normal) memory in the
-		balloon.

Documentation/ABI/stable/sysfs-driver-ib_srp

@@ -1,176 +0,0 @@
-What:		/sys/class/infiniband_srp/srp-<hca>-<port_number>/add_target
-Date:		January 2, 2006
-KernelVersion:	2.6.15
-Contact:	linux-rdma@vger.kernel.org
-Description:	Interface for making ib_srp connect to a new target.
-		One can request ib_srp to connect to a new target by writing
-		a comma-separated list of login parameters to this sysfs
-		attribute. The supported parameters are:
-		* id_ext, a 16-digit hexadecimal number specifying the eight
-		  byte identifier extension in the 16-byte SRP target port
-		  identifier. The target port identifier is sent by ib_srp
-		  to the target in the SRP_LOGIN_REQ request.
-		* ioc_guid, a 16-digit hexadecimal number specifying the eight
-		  byte I/O controller GUID portion of the 16-byte target port
-		  identifier.
-		* dgid, a 32-digit hexadecimal number specifying the
-		  destination GID.
-		* pkey, a four-digit hexadecimal number specifying the
-		  InfiniBand partition key.
-		* service_id, a 16-digit hexadecimal number specifying the
-		  InfiniBand service ID used to establish communication with
-		  the SRP target. How to find out the value of the service ID
-		  is specified in the documentation of the SRP target.
-		* max_sect, a decimal number specifying the maximum number of
-		  512-byte sectors to be transferred via a single SCSI command.
-		* max_cmd_per_lun, a decimal number specifying the maximum
-		  number of outstanding commands for a single LUN.
-		* io_class, a hexadecimal number specifying the SRP I/O class.
-		  Must be either 0xff00 (rev 10) or 0x0100 (rev 16a). The I/O
-		  class defines the format of the SRP initiator and target
-		  port identifiers.
-		* initiator_ext, a 16-digit hexadecimal number specifying the
-		  identifier extension portion of the SRP initiator port
-		  identifier. This data is sent by the initiator to the target
-		  in the SRP_LOGIN_REQ request.
-		* cmd_sg_entries, a number in the range 1..255 that specifies
-		  the maximum number of data buffer descriptors stored in the
-		  SRP_CMD information unit itself. With allow_ext_sg=0 the
-		  parameter cmd_sg_entries defines the maximum S/G list length
-		  for a single SRP_CMD, and commands whose S/G list length
-		  exceeds this limit after S/G list collapsing will fail.
-		* allow_ext_sg, whether ib_srp is allowed to include a partial
-		  memory descriptor list in an SRP_CMD instead of the entire
-		  list. If a partial memory descriptor list has been included
-		  in an SRP_CMD the remaining memory descriptors are
-		  communicated from initiator to target via an additional RDMA
-		  transfer. Setting allow_ext_sg to 1 increases the maximum
-		  amount of data that can be transferred between initiator and
-		  target via a single SCSI command. Since not all SRP target
-		  implementations support partial memory descriptor lists the
-		  default value for this option is 0.
-		* sg_tablesize, a number in the range 1..2048 specifying the
-		  maximum S/G list length the SCSI layer is allowed to pass to
-		  ib_srp. Specifying a value that exceeds cmd_sg_entries is
-		  only safe with partial memory descriptor list support enabled
-		  (allow_ext_sg=1).
-		* comp_vector, a number in the range 0..n-1 specifying the
-		  MSI-X completion vector. Some HCA's allocate multiple (n)
-		  MSI-X vectors per HCA port. If the IRQ affinity masks of
-		  these interrupts have been configured such that each MSI-X
-		  interrupt is handled by a different CPU then the comp_vector
-		  parameter can be used to spread the SRP completion workload
-		  over multiple CPU's.
-		* tl_retry_count, a number in the range 2..7 specifying the
-		  IB RC retry count.
-		* queue_size, the maximum number of commands that the
-		  initiator is allowed to queue per SCSI host. The default
-		  value for this parameter is 62. The lowest supported value
-		  is 2.
-
-What:		/sys/class/infiniband_srp/srp-<hca>-<port_number>/ibdev
-Date:		January 2, 2006
-KernelVersion:	2.6.15
-Contact:	linux-rdma@vger.kernel.org
-Description:	HCA name (<hca>).
-
-What:		/sys/class/infiniband_srp/srp-<hca>-<port_number>/port
-Date:		January 2, 2006
-KernelVersion:	2.6.15
-Contact:	linux-rdma@vger.kernel.org
-Description:	HCA port number (<port_number>).
-
-What:		/sys/class/scsi_host/host<n>/allow_ext_sg
-Date:		May 19, 2011
-KernelVersion:	2.6.39
-Contact:	linux-rdma@vger.kernel.org
-Description:	Whether ib_srp is allowed to include a partial memory
-		descriptor list in an SRP_CMD when communicating with an SRP
-		target.
-
-What:		/sys/class/scsi_host/host<n>/cmd_sg_entries
-Date:		May 19, 2011
-KernelVersion:	2.6.39
-Contact:	linux-rdma@vger.kernel.org
-Description:	Maximum number of data buffer descriptors that may be sent to
-		the target in a single SRP_CMD request.
-
-What:		/sys/class/scsi_host/host<n>/dgid
-Date:		June 17, 2006
-KernelVersion:	2.6.17
-Contact:	linux-rdma@vger.kernel.org
-Description:	InfiniBand destination GID used for communication with the SRP
-		target. Differs from orig_dgid if port redirection has happened.
-
-What:		/sys/class/scsi_host/host<n>/id_ext
-Date:		June 17, 2006
-KernelVersion:	2.6.17
-Contact:	linux-rdma@vger.kernel.org
-Description:	Eight-byte identifier extension portion of the 16-byte target
-		port identifier.
-
-What:		/sys/class/scsi_host/host<n>/ioc_guid
-Date:		June 17, 2006
-KernelVersion:	2.6.17
-Contact:	linux-rdma@vger.kernel.org
-Description:	Eight-byte I/O controller GUID portion of the 16-byte target
-		port identifier.
-
-What:		/sys/class/scsi_host/host<n>/local_ib_device
-Date:		November 29, 2006
-KernelVersion:	2.6.19
-Contact:	linux-rdma@vger.kernel.org
-Description:	Name of the InfiniBand HCA used for communicating with the
-		SRP target.
-
-What:		/sys/class/scsi_host/host<n>/local_ib_port
-Date:		November 29, 2006
-KernelVersion:	2.6.19
-Contact:	linux-rdma@vger.kernel.org
-Description:	Number of the HCA port used for communicating with the
-		SRP target.
-
-What:		/sys/class/scsi_host/host<n>/orig_dgid
-Date:		June 17, 2006
-KernelVersion:	2.6.17
-Contact:	linux-rdma@vger.kernel.org
-Description:	InfiniBand destination GID specified in the parameters
-		written to the add_target sysfs attribute.
-
-What:		/sys/class/scsi_host/host<n>/pkey
-Date:		June 17, 2006
-KernelVersion:	2.6.17
-Contact:	linux-rdma@vger.kernel.org
-Description:	A 16-bit number representing the InfiniBand partition key used
-		for communication with the SRP target.
-
-What:		/sys/class/scsi_host/host<n>/req_lim
-Date:		October 20, 2010
-KernelVersion:	2.6.36
-Contact:	linux-rdma@vger.kernel.org
-Description:	Number of requests ib_srp can send to the target before it has
-		to wait for more credits. For more information see also the
-		SRP credit algorithm in the SRP specification.
-
-What:		/sys/class/scsi_host/host<n>/service_id
-Date:		June 17, 2006
-KernelVersion:	2.6.17
-Contact:	linux-rdma@vger.kernel.org
-Description:	InfiniBand service ID used for establishing communication with
-		the SRP	target.
-
-What:		/sys/class/scsi_host/host<n>/sgid
-Date:		February 1, 2014
-KernelVersion:	3.13
-Contact:	linux-rdma@vger.kernel.org
-Description:	InfiniBand GID of the source port used for communication with
-		the SRP target.
-
-What:		/sys/class/scsi_host/host<n>/zero_req_lim
-Date:		September 20, 2006
-KernelVersion:	2.6.18
-Contact:	linux-rdma@vger.kernel.org
-Description:	Number of times the initiator had to wait before sending a
-		request to the target because it ran out of credits. For more
-		information see also the SRP credit algorithm in the SRP
-		specification.

Documentation/ABI/stable/sysfs-driver-usb-usbtmc

@@ -1,7 +1,7 @@
-What:		/sys/bus/usb/drivers/usbtmc/*/interface_capabilities
-What:		/sys/bus/usb/drivers/usbtmc/*/device_capabilities
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/interface_capabilities
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/device_capabilities
 Date:		August 2008
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
 		These files show the various USB TMC capabilities as described
 		by the device itself.  The full description of the bitfields
@@ -12,10 +12,10 @@ Description:
 		The files are read only.
 
 
-What:		/sys/bus/usb/drivers/usbtmc/*/usb488_interface_capabilities
-What:		/sys/bus/usb/drivers/usbtmc/*/usb488_device_capabilities
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/usb488_interface_capabilities
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/usb488_device_capabilities
 Date:		August 2008
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
 		These files show the various USB TMC capabilities as described
 		by the device itself.  The full description of the bitfields
@@ -27,9 +27,9 @@ Description:
 		The files are read only.
 
 
-What:		/sys/bus/usb/drivers/usbtmc/*/TermChar
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/TermChar
 Date:		August 2008
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
 		This file is the TermChar value to be sent to the USB TMC
 		device as described by the document, "Universal Serial Bus Test
@@ -40,9 +40,9 @@ Description:
 		sent to the device or not.
 
 
-What:		/sys/bus/usb/drivers/usbtmc/*/TermCharEnabled
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/TermCharEnabled
 Date:		August 2008
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
 		This file determines if the TermChar is to be sent to the
 		device on every transaction or not.  For more details about
@@ -51,11 +51,11 @@ Description:
 		published by the USB-IF.
 
 
-What:		/sys/bus/usb/drivers/usbtmc/*/auto_abort
+What:		/sys/bus/usb/drivers/usbtmc/devices/*/auto_abort
 Date:		August 2008
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
-		This file determines if the transaction of the USB TMC
+		This file determines if the the transaction of the USB TMC
 		device is to be automatically aborted if there is any error.
 		For more details about this, please see the document,
 		"Universal Serial Bus Test and Measurement Class Specification

Documentation/ABI/stable/sysfs-driver-w1_ds28e04

@@ -1,15 +0,0 @@
-What:		/sys/bus/w1/devices/.../pio
-Date:		May 2012
-Contact:	Markus Franke <franm@hrz.tu-chemnitz.de>
-Description:	read/write the contents of the two PIO's of the DS28E04-100
-		see Documentation/w1/slaves/w1_ds28e04 for detailed information
-Users:		any user space application which wants to communicate with DS28E04-100
-
-
-
-What:		/sys/bus/w1/devices/.../eeprom
-Date:		May 2012
-Contact:	Markus Franke <franm@hrz.tu-chemnitz.de>
-Description:	read/write the contents of the EEPROM memory of the DS28E04-100
-		see Documentation/w1/slaves/w1_ds28e04 for detailed information
-Users:		any user space application which wants to communicate with DS28E04-100

Documentation/ABI/stable/sysfs-firmware-opal-dump

@@ -1,41 +0,0 @@
-What:		/sys/firmware/opal/dump
-Date:		Feb 2014
-Contact:	Stewart Smith <stewart@linux.vnet.ibm.com>
-Description:
-		This directory exposes interfaces for interacting with
-		the FSP and platform dumps through OPAL firmware interface.
-
-		This is only for the powerpc/powernv platform.
-
-		initiate_dump:	When '1' is written to it,
-				we will initiate a dump.
-				Read this file for supported commands.
-
-		0xXX-0xYYYY:	A directory for dump of type 0xXX and
-				id 0xYYYY (in hex). The name of this
-				directory should not be relied upon to
-				be in this format, only that it's unique
-				among all dumps. For determining the type
-				and ID of the dump, use the id and type files.
-				Do not rely on any particular size of dump
-				type or dump id.
-
-		Each dump has the following files:
-		id:		An ASCII representation of the dump ID
-				in hex (e.g. '0x01')
-		type:		An ASCII representation of the type of
-				dump in the format "0x%x %s" with the ID
-				in hex and a description of the dump type
-				(or 'unknown').
-				Type '0xffffffff unknown' is used when
-				we could not get the type from firmware.
-				e.g. '0x02 System/Platform Dump'
-		dump:		A binary file containing the dump.
-				The size of the dump is the size of this file.
-		acknowledge:	When 'ack' is written to this, we will
-				acknowledge that we've retrieved the
-				dump to the service processor. It will
-				then remove it, making the dump
-				inaccessible.
-				Reading this file will get a list of
-				supported actions.

Documentation/ABI/stable/sysfs-firmware-opal-elog

@@ -1,60 +0,0 @@
-What:		/sys/firmware/opal/elog
-Date:		Feb 2014
-Contact:	Stewart Smith <stewart@linux.vnet.ibm.com>
-Description:
-		This directory exposes error log entries retrieved
-		through the OPAL firmware interface.
-
-		Each error log is identified by a unique ID and will
-		exist until explicitly acknowledged to firmware.
-
-		Each log entry has a directory in /sys/firmware/opal/elog.
-
-		Log entries may be purged by the service processor
-		before retrieved by firmware or retrieved/acknowledged by
-		Linux if there is no room for more log entries.
-
-		In the event that Linux has retrieved the log entries
-		but not explicitly acknowledged them to firmware and
-		the service processor needs more room for log entries,
-		the only remaining copy of a log message may be in
-		Linux.
-
-		Typically, a user space daemon will monitor for new
-		entries, read them out and acknowledge them.
-
-		The service processor may be able to store more log
-		entries than firmware can, so after you acknowledge
-		an event from Linux you may instantly get another one
-		from the queue that was generated some time in the past.
-
-		The raw log format is a binary format. We currently
-		do not parse this at all in kernel, leaving it up to
-		user space to solve the problem. In future, we may
-		do more parsing in kernel and add more files to make
-		it easier for simple user space processes to extract
-		more information.
-
-		For each log entry (directory), there are the following
-		files:
-
-		id:		An ASCII representation of the ID of the
-				error log, in hex - e.g. "0x01".
-
-		type:		An ASCII representation of the type id and
-				description of the type of error log.
-				Currently just "0x00 PEL" - platform error log.
-				In the future there may be additional types.
-
-		raw:		A read-only binary file that can be read
-				to get the raw log entry. These are
-				<16kb, often just hundreds of bytes and
-				"average" 2kb.
-
-		acknowledge:	Writing 'ack' to this file will acknowledge
-				the error log to firmware (and in turn
-				the service processor, if applicable).
-				Shortly after acknowledging it, the log
-				entry will be removed from sysfs.
-				Reading this file will list the supported
-				operations (curently just acknowledge).

Documentation/ABI/stable/sysfs-module

@@ -4,13 +4,9 @@ Description:
 
 	/sys/module/MODULENAME
 		The name of the module that is in the kernel.  This
-		module name will always show up if the module is loaded as a
-		dynamic module.  If it is built directly into the kernel, it
-		will only show up if it has a version or at least one
-		parameter.
-
-		Note: The conditions of creation in the built-in case are not
-		by design and may be removed in the future.
+		module name will show up either if the module is built
+		directly into the kernel, or if it is loaded as a
+		dyanmic module.
 
 	/sys/module/MODULENAME/parameters
 		This directory contains individual files that are each

Documentation/ABI/stable/sysfs-transport-srp

@@ -1,58 +0,0 @@
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/delete
-Date:		June 1, 2012
-KernelVersion:	3.7
-Contact:	linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
-Description:	Instructs an SRP initiator to disconnect from a target and to
-		remove all LUNs imported from that target.
-
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/dev_loss_tmo
-Date:		February 1, 2014
-KernelVersion:	3.13
-Contact:	linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
-Description:	Number of seconds the SCSI layer will wait after a transport
-		layer error has been observed before removing a target port.
-		Zero means immediate removal. Setting this attribute to "off"
-		will disable the dev_loss timer.
-
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/fast_io_fail_tmo
-Date:		February 1, 2014
-KernelVersion:	3.13
-Contact:	linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
-Description:	Number of seconds the SCSI layer will wait after a transport
-		layer error has been observed before failing I/O. Zero means
-		failing I/O immediately. Setting this attribute to "off" will
-		disable the fast_io_fail timer.
-
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/port_id
-Date:		June 27, 2007
-KernelVersion:	2.6.24
-Contact:	linux-scsi@vger.kernel.org
-Description:	16-byte local SRP port identifier in hexadecimal format. An
-		example: 4c:49:4e:55:58:20:56:49:4f:00:00:00:00:00:00:00.
-
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/reconnect_delay
-Date:		February 1, 2014
-KernelVersion:	3.13
-Contact:	linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
-Description:	Number of seconds the SCSI layer will wait after a reconnect
-		attempt failed before retrying. Setting this attribute to
-		"off" will disable time-based reconnecting.
-
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/roles
-Date:		June 27, 2007
-KernelVersion:	2.6.24
-Contact:	linux-scsi@vger.kernel.org
-Description:	Role of the remote port. Either "SRP Initiator" or "SRP Target".
-
-What:		/sys/class/srp_remote_ports/port-<h>:<n>/state
-Date:		February 1, 2014
-KernelVersion:	3.13
-Contact:	linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
-Description:	State of the transport layer used for communication with the
-		remote port. "running" if the transport layer is operational;
-		"blocked" if a transport layer error has been encountered but
-		the fast_io_fail_tmo timer has not yet fired; "fail-fast"
-		after the fast_io_fail_tmo timer has fired and before the
-		"dev_loss_tmo" timer has fired; "lost" after the
-		"dev_loss_tmo" timer has fired and before the port is finally
-		removed.

Documentation/ABI/stable/vdso

@@ -24,4 +24,4 @@ though.
 
 (As of this writing, this ABI documentation as been confirmed for x86_64.
  The maintainers of the other vDSO-using architectures should confirm
- that it is correct for their architecture.)
+ that it is correct for their architecture.)

Documentation/ABI/testing/configfs-usb-gadget

@@ -1,126 +0,0 @@
-What:		/config/usb-gadget
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		This group contains sub-groups corresponding to created
-		USB gadgets.
-
-What:		/config/usb-gadget/gadget
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-
-		The attributes of a gadget:
-
-		UDC		- bind a gadget to UDC/unbind a gadget;
-				write UDC's name found in /sys/class/udc/*
-				to bind a gadget, empty string "" to unbind.
-
-		bDeviceClass	- USB device class code
-		bDeviceSubClass	- USB device subclass code
-		bDeviceProtocol	- USB device protocol code
-		bMaxPacketSize0	- maximum endpoint 0 packet size
-		bcdDevice	- bcd device release number
-		bcdUSB		- bcd USB specification version number
-		idProduct	- product ID
-		idVendor	- vendor ID
-
-What:		/config/usb-gadget/gadget/configs
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		This group contains a USB gadget's configurations
-
-What:		/config/usb-gadget/gadget/configs/config
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes of a configuration:
-
-		bmAttributes	- configuration characteristics
-		MaxPower	- maximum power consumption from the bus
-
-What:		/config/usb-gadget/gadget/configs/config/strings
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		This group contains subdirectories for language-specific
-		strings for this configuration.
-
-What:		/config/usb-gadget/gadget/configs/config/strings/language
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		configuration	- configuration description
-
-
-What:		/config/usb-gadget/gadget/functions
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		This group contains functions available to this USB gadget.
-
-What:		/config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>
-Date:		May 2014
-KernelVersion:	3.16
-Description:
-		This group contains "Feature Descriptors" specific for one
-		gadget's USB interface or one interface group described
-		by an IAD.
-
-		The attributes:
-
-		compatible_id		- 8-byte string for "Compatible ID"
-		sub_compatible_id	- 8-byte string for "Sub Compatible ID"
-
-What:		/config/usb-gadget/gadget/functions/<func>.<inst>/interface.<n>/<property>
-Date:		May 2014
-KernelVersion:	3.16
-Description:
-		This group contains "Extended Property Descriptors" specific for one
-		gadget's USB interface or one interface group described
-		by an IAD.
-
-		The attributes:
-
-		type		- value 1..7 for interpreting the data
-				1: unicode string
-				2: unicode string with environment variable
-				3: binary
-				4: little-endian 32-bit
-				5: big-endian 32-bit
-				6: unicode string with a symbolic link
-				7: multiple unicode strings
-		data		- blob of data to be interpreted depending on
-				type
-
-What:		/config/usb-gadget/gadget/strings
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		This group contains subdirectories for language-specific
-		strings for this gadget.
-
-What:		/config/usb-gadget/gadget/strings/language
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		serialnumber	- gadget's serial number (string)
-		product		- gadget's product description
-		manufacturer	- gadget's manufacturer description
-
-What:		/config/usb-gadget/gadget/os_desc
-Date:		May 2014
-KernelVersion:	3.16
-Description:
-		This group contains "OS String" extension handling attributes.
-
-		use		- flag turning "OS Desctiptors" support on/off
-		b_vendor_code	- one-byte value used for custom per-device and
-				per-interface requests
-		qw_sign		- an identifier to be reported as "OS String"
-				proper

Documentation/ABI/testing/configfs-usb-gadget-acm

@@ -1,8 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/acm.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-
-		This item contains just one readonly attribute: port_num.
-		It contains the port number of the /dev/ttyGS<n> device
-		associated with acm function's instance "name".

Documentation/ABI/testing/configfs-usb-gadget-ecm

@@ -1,16 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/ecm.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		ifname		- network device interface name associated with
-				this function instance
-		qmult		- queue length multiplier for high and
-				super speed
-		host_addr	- MAC address of host's end of this
-				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
-				Ethernet over USB link
-
-

Documentation/ABI/testing/configfs-usb-gadget-eem

@@ -1,14 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/eem.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		ifname		- network device interface name associated with
-				this function instance
-		qmult		- queue length multiplier for high and
-				super speed
-		host_addr	- MAC address of host's end of this
-				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
-				Ethernet over USB link

Documentation/ABI/testing/configfs-usb-gadget-ffs

@@ -1,9 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/ffs.name
-Date:		Nov 2013
-KernelVersion:	3.13
-Description:	The purpose of this directory is to create and remove it.
-
-		A corresponding USB function instance is created/removed.
-		There are no attributes here.
-
-		All parameters are set through FunctionFS.

Documentation/ABI/testing/configfs-usb-gadget-loopback

@@ -1,8 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/Loopback.name
-Date:		Nov 2013
-KernelVersion:	3.13
-Description:
-		The attributes:
-
-		qlen		- depth of loopback queue
-		bulk_buflen	- buffer length

Documentation/ABI/testing/configfs-usb-gadget-mass-storage

@@ -1,31 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/mass_storage.name
-Date:		Oct 2013
-KernelVersion:	3.13
-Description:
-		The attributes:
-
-		stall		- Set to permit function to halt bulk endpoints.
-				Disabled on some USB devices known not to work
-				correctly. You should set it to true.
-		num_buffers	- Number of pipeline buffers. Valid numbers
-				are 2..4. Available only if
-				CONFIG_USB_GADGET_DEBUG_FILES is set.
-
-What:		/config/usb-gadget/gadget/functions/mass_storage.name/lun.name
-Date:		Oct 2013
-KernelVersion:	3.13
-Description:
-		The attributes:
-
-		file		- The path to the backing file for the LUN.
-				Required if LUN is not marked as removable.
-		ro		- Flag specifying access to the LUN shall be
-				read-only. This is implied if CD-ROM emulation
-				is enabled as well as when it was impossible
-				to open "filename" in R/W mode.
-		removable	- Flag specifying that LUN shall be indicated as
-				being removable.
-		cdrom		- Flag specifying that LUN shall be reported as
-				being a CD-ROM.
-		nofua		- Flag specifying that FUA flag
-				in SCSI WRITE(10,12)

Documentation/ABI/testing/configfs-usb-gadget-ncm

@@ -1,15 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/ncm.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		ifname		- network device interface name associated with
-				this function instance
-		qmult		- queue length multiplier for high and
-				super speed
-		host_addr	- MAC address of host's end of this
-				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
-				Ethernet over USB link
-

Documentation/ABI/testing/configfs-usb-gadget-obex

@@ -1,9 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/obex.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-
-		This item contains just one readonly attribute: port_num.
-		It contains the port number of the /dev/ttyGS<n> device
-		associated with obex function's instance "name".
-

Documentation/ABI/testing/configfs-usb-gadget-phonet

@@ -1,8 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/phonet.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-
-		This item contains just one readonly attribute: ifname.
-		It contains the network interface name assigned during
-		network device registration.

Documentation/ABI/testing/configfs-usb-gadget-rndis

@@ -1,14 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/rndis.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		ifname		- network device interface name associated with
-				this function instance
-		qmult		- queue length multiplier for high and
-				super speed
-		host_addr	- MAC address of host's end of this
-				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
-				Ethernet over USB link

Documentation/ABI/testing/configfs-usb-gadget-serial

@@ -1,9 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/gser.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-
-		This item contains just one readonly attribute: port_num.
-		It contains the port number of the /dev/ttyGS<n> device
-		associated with gser function's instance "name".
-

Documentation/ABI/testing/configfs-usb-gadget-sourcesink

@@ -1,12 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/SourceSink.name
-Date:		Nov 2013
-KernelVersion:	3.13
-Description:
-		The attributes:
-
-		pattern		- 0 (all zeros), 1 (mod63), 2 (none)
-		isoc_interval	- 1..16
-		isoc_maxpacket	- 0 - 1023 (fs), 0 - 1024 (hs/ss)
-		isoc_mult	- 0..2 (hs/ss only)
-		isoc_maxburst	- 0..15 (ss only)
-		qlen		- buffer length

Documentation/ABI/testing/configfs-usb-gadget-subset

@@ -1,14 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/geth.name
-Date:		Jun 2013
-KernelVersion:	3.11
-Description:
-		The attributes:
-
-		ifname		- network device interface name associated with
-				this function instance
-		qmult		- queue length multiplier for high and
-				super speed
-		host_addr	- MAC address of host's end of this
-				Ethernet over USB link
-		dev_addr	- MAC address of device's end of this
-				Ethernet over USB link

Documentation/ABI/testing/configfs-usb-gadget-uac1

@@ -1,12 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/uac1.name
-Date:		Sep 2014
-KernelVersion:	3.18
-Description:
-		The attributes:
-
-		audio_buf_size - audio buffer size
-		fn_cap - capture pcm device file name
-		fn_cntl - control device file name
-		fn_play - playback pcm device file name
-		req_buf_size - ISO OUT endpoint request buffer size
-		req_count - ISO OUT endpoint request count

Documentation/ABI/testing/configfs-usb-gadget-uac2

@@ -1,12 +0,0 @@
-What:		/config/usb-gadget/gadget/functions/uac2.name
-Date:		Sep 2014
-KernelVersion:	3.18
-Description:
-		The attributes:
-
-		c_chmask - capture channel mask
-		c_srate - capture sampling rate
-		c_ssize - capture sample size (bytes)
-		p_chmask - playback channel mask
-		p_srate - playback sampling rate
-		p_ssize - playback sample size (bytes)

Documentation/ABI/testing/debugfs-driver-genwqe

@@ -1,91 +0,0 @@
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/ddcb_info
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    DDCB queue dump used for debugging queueing problems.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/curr_regs
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Dump of the current error registers.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid0
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Internal chip state of UID0 (unit id 0).
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid1
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Internal chip state of UID1.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid2
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Internal chip state of UID2.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/prev_regs
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Dump of the error registers before the last reset of
-                the card occured.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid0
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Internal chip state of UID0 before card was reset.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid1
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Internal chip state of UID1 before card was reset.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid2
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Internal chip state of UID2 before card was reset.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/info
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Comprehensive summary of bitstream version and software
-                version. Used bitstream and bitstream clocking information.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/err_inject
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Possibility to inject error cases to ensure that the drivers
-                error handling code works well.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/vf<0..14>_jobtimeout_msec
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Default VF timeout 250ms. Testing might require 1000ms.
-                Using 0 will use the cards default value (whatever that is).
-
-                The timeout depends on the max number of available cards
-                in the system and the maximum allowed queue size.
-
-                The driver ensures that the settings are done just before
-                the VFs get enabled. Changing the timeouts in flight is not
-                possible.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/jobtimer
-Date:           Oct 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Dump job timeout register values for PF and VFs.
-                Only available for PF.
-
-What:           /sys/kernel/debug/genwqe/genwqe<n>_card/queue_working_time
-Date:           Dec 2013
-Contact:        haver@linux.vnet.ibm.com
-Description:    Dump queue working time register values for PF and VFs.
-                Only available for PF.

Documentation/ABI/testing/debugfs-olpc

@@ -1,16 +0,0 @@
-What:		/sys/kernel/debug/olpc-ec/cmd
-Date:		Dec 2011
-KernelVersion:	3.4
-Contact:	devel@lists.laptop.org
-Description:
-
-A generic interface for executing OLPC Embedded Controller commands and
-reading their responses.
-
-To execute a command, write data with the format: CC:N A A A A
-CC is the (hex) command, N is the count of expected reply bytes, and A A A A
-are optional (hex) arguments.
-
-To read the response (if any), read from the generic node after executing
-a command. Hex reply bytes will be returned, *whether or not* they came from
-the immediately previous command.

Documentation/ABI/testing/debugfs-pfo-nx-crypto

@@ -1,45 +0,0 @@
-What:		/sys/kernel/debug/nx-crypto/*
-Date:		March 2012
-KernelVersion:	3.4
-Contact:	Kent Yoder <key@linux.vnet.ibm.com>
-Description:
-
-  These debugfs interfaces are built by the nx-crypto driver, built in
-arch/powerpc/crypto/nx.
-
-Error Detection
-===============
-
-errors:
-- A u32 providing a total count of errors since the driver was loaded. The
-only errors counted here are those returned from the hcall, H_COP_OP.
-
-last_error:
-- The most recent non-zero return code from the H_COP_OP hcall. -EBUSY is not
-recorded here (the hcall will retry until -EBUSY goes away).
-
-last_error_pid:
-- The process ID of the process who received the most recent error from the
-hcall.
-
-Device Use
-==========
-
-aes_bytes:
-- The total number of bytes encrypted using AES in any of the driver's
-supported modes.
-
-aes_ops:
-- The total number of AES operations submitted to the hardware.
-
-sha256_bytes:
-- The total number of bytes hashed by the hardware using SHA-256.
-
-sha256_ops:
-- The total number of SHA-256 operations submitted to the hardware.
-
-sha512_bytes:
-- The total number of bytes hashed by the hardware using SHA-512.
-
-sha512_ops:
-- The total number of SHA-512 operations submitted to the hardware.

Documentation/ABI/testing/dev-kmsg

@@ -1,101 +0,0 @@
-What:		/dev/kmsg
-Date:		Mai 2012
-KernelVersion:	3.5
-Contact:	Kay Sievers <kay@vrfy.org>
-Description:	The /dev/kmsg character device node provides userspace access
-		to the kernel's printk buffer.
-
-		Injecting messages:
-		Every write() to the opened device node places a log entry in
-		the kernel's printk buffer.
-
-		The logged line can be prefixed with a <N> syslog prefix, which
-		carries the syslog priority and facility. The single decimal
-		prefix number is composed of the 3 lowest bits being the syslog
-		priority and the higher bits the syslog facility number.
-
-		If no prefix is given, the priority number is the default kernel
-		log priority and the facility number is set to LOG_USER (1). It
-		is not possible to inject messages from userspace with the
-		facility number LOG_KERN (0), to make sure that the origin of
-		the messages can always be reliably determined.
-
-		Accessing the buffer:
-		Every read() from the opened device node receives one record
-		of the kernel's printk buffer.
-
-		The first read() directly following an open() always returns
-		first message in the buffer; there is no kernel-internal
-		persistent state; many readers can concurrently open the device
-		and read from it, without affecting other readers.
-
-		Every read() will receive the next available record. If no more
-		records are available read() will block, or if O_NONBLOCK is
-		used -EAGAIN returned.
-
-		Messages in the record ring buffer get overwritten as whole,
-		there are never partial messages received by read().
-
-		In case messages get overwritten in the circular buffer while
-		the device is kept open, the next read() will return -EPIPE,
-		and the seek position be updated to the next available record.
-		Subsequent reads() will return available records again.
-
-		Unlike the classic syslog() interface, the 64 bit record
-		sequence numbers allow to calculate the amount of lost
-		messages, in case the buffer gets overwritten. And they allow
-		to reconnect to the buffer and reconstruct the read position
-		if needed, without limiting the interface to a single reader.
-
-		The device supports seek with the following parameters:
-		SEEK_SET, 0
-		  seek to the first entry in the buffer
-		SEEK_END, 0
-		  seek after the last entry in the buffer
-		SEEK_DATA, 0
-		  seek after the last record available at the time
-		  the last SYSLOG_ACTION_CLEAR was issued.
-
-		The output format consists of a prefix carrying the syslog
-		prefix including priority and facility, the 64 bit message
-		sequence number and the monotonic timestamp in microseconds,
-		and a flag field. All fields are separated by a ','.
-
-		Future extensions might add more comma separated values before
-		the terminating ';'. Unknown fields and values should be
-		gracefully ignored.
-
-		The human readable text string starts directly after the ';'
-		and is terminated by a '\n'. Untrusted values derived from
-		hardware or other facilities are printed, therefore
-		all non-printable characters and '\' itself in the log message
-		are escaped by "\x00" C-style hex encoding.
-
-		A line starting with ' ', is a continuation line, adding
-		key/value pairs to the log message, which provide the machine
-		readable context of the message, for reliable processing in
-		userspace.
-
-		Example:
-		7,160,424069,-;pci_root PNP0A03:00: host bridge window [io  0x0000-0x0cf7] (ignored)
-		 SUBSYSTEM=acpi
-		 DEVICE=+acpi:PNP0A03:00
-		6,339,5140900,-;NET: Registered protocol family 10
-		30,340,5690716,-;udevd[80]: starting version 181
-
-		The DEVICE= key uniquely identifies devices the following way:
-		  b12:8        - block dev_t
-		  c127:3       - char dev_t
-		  n8           - netdev ifindex
-		  +sound:card0 - subsystem:devname
-
-		The flags field carries '-' by default. A 'c' indicates a
-		fragment of a line. All following fragments are flagged with
-		'+'. Note, that these hints about continuation lines are not
-		necessarily correct, and the stream could be interleaved with
-		unrelated messages, but merging the lines in the output
-		usually produces better human readable results. A similar
-		logic is used internally when messages are printed to the
-		console, /proc/kmsg or the syslog() syscall.
-
-Users:		dmesg(1), userspace kernel log consumers

Documentation/ABI/testing/ima_policy

@@ -12,72 +12,48 @@ Description:
 		then closing the file.  The new policy takes effect after
 		the file ima/policy is closed.
 
-		IMA appraisal, if configured, uses these file measurements
-		for local measurement appraisal.
-
 		rule format: action [condition ...]
 
-		action: measure | dont_measure | appraise | dont_appraise | audit
-		condition:= base | lsm  [option]
-			base:	[[func=] [mask=] [fsmagic=] [fsuuid=] [uid=]
-				 [fowner]]
+		action: measure | dont_measure
+		condition:= base | lsm
+			base:	[[func=] [mask=] [fsmagic=] [uid=]]
 			lsm:	[[subj_user=] [subj_role=] [subj_type=]
 				 [obj_user=] [obj_role=] [obj_type=]]
-			option:	[[appraise_type=]] [permit_directio]
 
-		base: 	func:= [BPRM_CHECK][MMAP_CHECK][FILE_CHECK][MODULE_CHECK]
-				[FIRMWARE_CHECK]
+		base: 	func:= [BPRM_CHECK][FILE_MMAP][FILE_CHECK]
 			mask:= [MAY_READ] [MAY_WRITE] [MAY_APPEND] [MAY_EXEC]
 			fsmagic:= hex value
-			fsuuid:= file system UUID (e.g 8bcbe394-4f13-4144-be8e-5aa9ea2ce2f6)
 			uid:= decimal value
-			fowner:=decimal value
 		lsm:  	are LSM specific
-		option:	appraise_type:= [imasig]
 
 		default policy:
 			# PROC_SUPER_MAGIC
 			dont_measure fsmagic=0x9fa0
-			dont_appraise fsmagic=0x9fa0
 			# SYSFS_MAGIC
 			dont_measure fsmagic=0x62656572
-			dont_appraise fsmagic=0x62656572
 			# DEBUGFS_MAGIC
 			dont_measure fsmagic=0x64626720
-			dont_appraise fsmagic=0x64626720
 			# TMPFS_MAGIC
 			dont_measure fsmagic=0x01021994
-			dont_appraise fsmagic=0x01021994
-			# RAMFS_MAGIC
-			dont_measure fsmagic=0x858458f6
-			dont_appraise fsmagic=0x858458f6
 			# SECURITYFS_MAGIC
 			dont_measure fsmagic=0x73636673
-			dont_appraise fsmagic=0x73636673
 
 			measure func=BPRM_CHECK
 			measure func=FILE_MMAP mask=MAY_EXEC
 			measure func=FILE_CHECK mask=MAY_READ uid=0
-			measure func=MODULE_CHECK
-			measure func=FIRMWARE_CHECK
-			appraise fowner=0
 
 		The default policy measures all executables in bprm_check,
 		all files mmapped executable in file_mmap, and all files
-		open for read by root in do_filp_open.  The default appraisal
-		policy appraises all files owned by root.
+		open for read by root in do_filp_open.
 
 		Examples of LSM specific definitions:
 
 		SELinux:
 			# SELINUX_MAGIC
-			dont_measure fsmagic=0xf97cff8c
-			dont_appraise fsmagic=0xf97cff8c
+			dont_measure fsmagic=0xF97CFF8C
 
 			dont_measure obj_type=var_log_t
-			dont_appraise obj_type=var_log_t
 			dont_measure obj_type=auditd_log_t
-			dont_appraise obj_type=auditd_log_t
 			measure subj_user=system_u func=FILE_CHECK mask=MAY_READ
 			measure subj_role=system_r func=FILE_CHECK mask=MAY_READ
 

Documentation/ABI/testing/pstore

@@ -1,4 +1,4 @@
-Where:		/sys/fs/pstore/... (or /dev/pstore/...)
+Where:		/dev/pstore/...
 Date:		March 2011
 Kernel Version: 2.6.39
 Contact:	tony.luck@intel.com
@@ -11,9 +11,9 @@ Description:	Generic interface to platform dependent persistent storage.
 		of the console log is captured, but other interesting
 		data can also be saved.
 
-		# mount -t pstore -o kmsg_bytes=8000 - /sys/fs/pstore
+		# mount -t pstore -o kmsg_bytes=8000 - /dev/pstore
 
-		$ ls -l /sys/fs/pstore/
+		$ ls -l /dev/pstore
 		total 0
 		-r--r--r-- 1 root root 7896 Nov 30 15:38 dmesg-erst-1
 
@@ -27,9 +27,9 @@ Description:	Generic interface to platform dependent persistent storage.
 		the file will signal to the underlying persistent storage
 		device that it can reclaim the space for later re-use.
 
-		$ rm /sys/fs/pstore/dmesg-erst-1
+		$ rm /dev/pstore/dmesg-erst-1
 
-		The expectation is that all files in /sys/fs/pstore/
+		The expectation is that all files in /dev/pstore
 		will be saved elsewhere and erased from persistent store
 		soon after boot to free up space ready for the next
 		catastrophe.

Documentation/ABI/testing/sysfs-block

@@ -53,14 +53,6 @@ Description:
 		512 bytes of data.
 
 
-What:		/sys/block/<disk>/integrity/device_is_integrity_capable
-Date:		July 2014
-Contact:	Martin K. Petersen <martin.petersen@oracle.com>
-Description:
-		Indicates whether a storage device is capable of storing
-		integrity metadata. Set if the device is T10 PI-capable.
-
-
 What:		/sys/block/<disk>/integrity/write_generate
 Date:		June 2008
 Contact:	Martin K. Petersen <martin.petersen@oracle.com>
@@ -214,17 +206,3 @@ Description:
 		when a discarded area is read the discard_zeroes_data
 		parameter will be set to one. Otherwise it will be 0 and
 		the result of reading a discarded area is undefined.
-
-What:		/sys/block/<disk>/queue/write_same_max_bytes
-Date:		January 2012
-Contact:	Martin K. Petersen <martin.petersen@oracle.com>
-Description:
-		Some devices support a write same operation in which a
-		single data block can be written to a range of several
-		contiguous blocks on storage. This can be used to wipe
-		areas on disk or to initialize drives in a RAID
-		configuration. write_same_max_bytes indicates how many
-		bytes can be written in a single write same command. If
-		write_same_max_bytes is 0, write same is not supported
-		by the device.
-

Documentation/ABI/testing/sysfs-block-bcache

@@ -1,156 +0,0 @@
-What:		/sys/block/<disk>/bcache/unregister
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		A write to this file causes the backing device or cache to be
-		unregistered. If a backing device had dirty data in the cache,
-		writeback mode is automatically disabled and all dirty data is
-		flushed before the device is unregistered. Caches unregister
-		all associated backing devices before unregistering themselves.
-
-What:		/sys/block/<disk>/bcache/clear_stats
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		Writing to this file resets all the statistics for the device.
-
-What:		/sys/block/<disk>/bcache/cache
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a backing device that has cache, a symlink to
-		the bcache/ dir of that cache.
-
-What:		/sys/block/<disk>/bcache/cache_hits
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: integer number of full cache hits,
-		counted per bio. A partial cache hit counts as a miss.
-
-What:		/sys/block/<disk>/bcache/cache_misses
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: integer number of cache misses.
-
-What:		/sys/block/<disk>/bcache/cache_hit_ratio
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: cache hits as a percentage.
-
-What:		/sys/block/<disk>/bcache/sequential_cutoff
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: Threshold past which sequential IO will
-		skip the cache. Read and written as bytes in human readable
-		units (i.e. echo 10M > sequntial_cutoff).
-
-What:		/sys/block/<disk>/bcache/bypassed
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		Sum of all reads and writes that have bypassed the cache (due
-		to the sequential cutoff).  Expressed as bytes in human
-		readable units.
-
-What:		/sys/block/<disk>/bcache/writeback
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: When on, writeback caching is enabled and
-		writes will be buffered in the cache. When off, caching is in
-		writethrough mode; reads and writes will be added to the
-		cache but no write buffering will take place.
-
-What:		/sys/block/<disk>/bcache/writeback_running
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: when off, dirty data will not be written
-		from the cache to the backing device. The cache will still be
-		used to buffer writes until it is mostly full, at which point
-		writes transparently revert to writethrough mode. Intended only
-		for benchmarking/testing.
-
-What:		/sys/block/<disk>/bcache/writeback_delay
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: In writeback mode, when dirty data is
-		written to the cache and the cache held no dirty data for that
-		backing device, writeback from cache to backing device starts
-		after this delay, expressed as an integer number of seconds.
-
-What:		/sys/block/<disk>/bcache/writeback_percent
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For backing devices: If nonzero, writeback from cache to
-		backing device only takes place when more than this percentage
-		of the cache is used, allowing more write coalescing to take
-		place and reducing total number of writes sent to the backing
-		device. Integer between 0 and 40.
-
-What:		/sys/block/<disk>/bcache/synchronous
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, a boolean that allows synchronous mode to be
-		switched on and off. In synchronous mode all writes are ordered
-		such that the cache can reliably recover from unclean shutdown;
-		if disabled bcache will not generally wait for writes to
-		complete but if the cache is not shut down cleanly all data
-		will be discarded from the cache. Should not be turned off with
-		writeback caching enabled.
-
-What:		/sys/block/<disk>/bcache/discard
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, a boolean allowing discard/TRIM to be turned off
-		or back on if the device supports it.
-
-What:		/sys/block/<disk>/bcache/bucket_size
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, bucket size in human readable units, as set at
-		cache creation time; should match the erase block size of the
-		SSD for optimal performance.
-
-What:		/sys/block/<disk>/bcache/nbuckets
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, the number of usable buckets.
-
-What:		/sys/block/<disk>/bcache/tree_depth
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, height of the btree excluding leaf nodes (i.e. a
-		one node tree will have a depth of 0).
-
-What:		/sys/block/<disk>/bcache/btree_cache_size
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		Number of btree buckets/nodes that are currently cached in
-		memory; cache dynamically grows and shrinks in response to
-		memory pressure from the rest of the system.
-
-What:		/sys/block/<disk>/bcache/written
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, total amount of data in human readable units
-		written to the cache, excluding all metadata.
-
-What:		/sys/block/<disk>/bcache/btree_written
-Date:		November 2010
-Contact:	Kent Overstreet <kent.overstreet@gmail.com>
-Description:
-		For a cache, sum of all btree writes in human readable units.

Documentation/ABI/testing/sysfs-block-dm

@@ -1,25 +0,0 @@
-What:		/sys/block/dm-<num>/dm/name
-Date:		January 2009
-KernelVersion:	2.6.29
-Contact:	dm-devel@redhat.com
-Description:	Device-mapper device name.
-		Read-only string containing mapped device name.
-Users:		util-linux, device-mapper udev rules
-
-What:		/sys/block/dm-<num>/dm/uuid
-Date:		January 2009
-KernelVersion:	2.6.29
-Contact:	dm-devel@redhat.com
-Description:	Device-mapper device UUID.
-		Read-only string containing DM-UUID or empty string
-		if DM-UUID is not set.
-Users:		util-linux, device-mapper udev rules
-
-What:		/sys/block/dm-<num>/dm/suspended
-Date:		June 2009
-KernelVersion:	2.6.31
-Contact:	dm-devel@redhat.com
-Description:	Device-mapper device suspend state.
-		Contains the value 1 while the device is suspended.
-		Otherwise it contains 0. Read-only attribute.
-Users:		util-linux, device-mapper udev rules

Documentation/ABI/testing/sysfs-block-rssd

@@ -1,5 +0,0 @@
-What:           /sys/block/rssd*/status
-Date:           April 2012
-KernelVersion:  3.4
-Contact:        Asai Thambi S P <asamymuthupa@micron.com>
-Description:    This is a read-only file. Indicates the status of the device.

Documentation/ABI/testing/sysfs-block-zram

@@ -5,21 +5,20 @@ Description:
 		The disksize file is read-write and specifies the disk size
 		which represents the limit on the *uncompressed* worth of data
 		that can be stored in this disk.
-		Unit: bytes
 
 What:		/sys/block/zram<id>/initstate
 Date:		August 2010
 Contact:	Nitin Gupta <ngupta@vflare.org>
 Description:
-		The initstate file is read-only and shows the initialization
+		The disksize file is read-only and shows the initialization
 		state of the device.
 
 What:		/sys/block/zram<id>/reset
 Date:		August 2010
 Contact:	Nitin Gupta <ngupta@vflare.org>
 Description:
-		The reset file is write-only and allows resetting the
-		device. The reset operation frees all the memory associated
+		The disksize file is write-only and allows resetting the
+		device. The reset operation frees all the memory assocaited
 		with this device.
 
 What:		/sys/block/zram<id>/num_reads
@@ -43,48 +42,24 @@ Description:
 		The invalid_io file is read-only and specifies the number of
 		non-page-size-aligned I/O requests issued to this device.
 
-What:		/sys/block/zram<id>/failed_reads
-Date:		February 2014
-Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-Description:
-		The failed_reads file is read-only and specifies the number of
-		failed reads happened on this device.
-
-What:		/sys/block/zram<id>/failed_writes
-Date:		February 2014
-Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-Description:
-		The failed_writes file is read-only and specifies the number of
-		failed writes happened on this device.
-
-What:		/sys/block/zram<id>/max_comp_streams
-Date:		February 2014
-Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-Description:
-		The max_comp_streams file is read-write and specifies the
-		number of backend's zcomp_strm compression streams (number of
-		concurrent compress operations).
-
-What:		/sys/block/zram<id>/comp_algorithm
-Date:		February 2014
-Contact:	Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
-Description:
-		The comp_algorithm file is read-write and lets to show
-		available and selected compression algorithms, change
-		compression algorithm selection.
-
 What:		/sys/block/zram<id>/notify_free
 Date:		August 2010
 Contact:	Nitin Gupta <ngupta@vflare.org>
 Description:
-		The notify_free file is read-only. Depending on device usage
-		scenario it may account a) the number of pages freed because
-		of swap slot free notifications or b) the number of pages freed
-		because of REQ_DISCARD requests sent by bio. The former ones
-		are sent to a swap block device when a swap slot is freed, which
-		implies that this disk is being used as a swap disk. The latter
-		ones are sent by filesystem mounted with discard option,
-		whenever some data blocks are getting discarded.
+		The notify_free file is read-only and specifies the number of
+		swap slot free notifications received by this device. These
+		notifications are send to a swap block device when a swap slot
+		is freed. This statistic is applicable only when this disk is
+		being used as a swap disk.
+
+What:		/sys/block/zram<id>/discard
+Date:		August 2010
+Contact:	Nitin Gupta <ngupta@vflare.org>
+Description:
+		The discard file is read-only and specifies the number of
+		discard requests received by this device. These requests
+		provide information to block device regarding blocks which are
+		no longer used by filesystem.
 
 What:		/sys/block/zram<id>/zero_pages
 Date:		August 2010
@@ -121,23 +96,4 @@ Description:
 		overhead, allocated for this disk. So, allocator space
 		efficiency can be calculated using compr_data_size and this
 		statistic.
-		Unit: bytes
-
-What:		/sys/block/zram<id>/mem_used_max
-Date:		August 2014
-Contact:	Minchan Kim <minchan@kernel.org>
-Description:
-		The mem_used_max file is read/write and specifies the amount
-		of maximum memory zram have consumed to store compressed data.
-		For resetting the value, you should write "0". Otherwise,
-		you could see -EINVAL.
-		Unit: bytes
-
-What:		/sys/block/zram<id>/mem_limit
-Date:		August 2014
-Contact:	Minchan Kim <minchan@kernel.org>
-Description:
-		The mem_limit file is read/write and specifies the maximum
-		amount of memory ZRAM can use to store the compressed data.  The
-		limit could be changed in run time and "0" means disable the
-		limit.  No limit is the initial state.  Unit: bytes
+		Unit: bytes

Documentation/ABI/testing/sysfs-bus-acpi

@@ -1,58 +0,0 @@
-What:		/sys/bus/acpi/devices/.../path
-Date:		December 2006
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		This attribute indicates the full path of ACPI namespace
-		object associated with the device object.  For example,
-		\_SB_.PCI0.
-		This file is not present for device objects representing
-		fixed ACPI hardware features (like power and sleep
-		buttons).
-
-What:		/sys/bus/acpi/devices/.../modalias
-Date:		July 2007
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		This attribute indicates the PNP IDs of the device object.
-		That is acpi:HHHHHHHH:[CCCCCCC:].  Where each HHHHHHHH or
-		CCCCCCCC contains device object's PNPID (_HID or _CID).
-
-What:		/sys/bus/acpi/devices/.../hid
-Date:		April 2005
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		This attribute indicates the hardware ID (_HID) of the
-		device object.  For example, PNP0103.
-		This file is present for device objects having the _HID
-		control method.
-
-What:		/sys/bus/acpi/devices/.../description
-Date:		October 2012
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		This attribute contains the output of the device object's
-		_STR control method, if present.
-
-What:		/sys/bus/acpi/devices/.../adr
-Date:		October 2012
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		This attribute contains the output of the device object's
-		_ADR control method, which is present for ACPI device
-		objects representing devices having standard enumeration
-		algorithms, such as PCI.
-
-What:		/sys/bus/acpi/devices/.../uid
-Date:		October 2012
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		This attribute contains the output of the device object's
-		_UID control method, if present.
-
-What:		/sys/bus/acpi/devices/.../eject
-Date:		December 2006
-Contact:	Rafael J. Wysocki <rjw@rjwysocki.net>
-Description:
-		Writing 1 to this attribute will trigger hot removal of
-		this device object.  This file exists for every device
-		object that has _EJ0 method.

Documentation/ABI/testing/sysfs-bus-event_source-devices-events

@@ -1,88 +0,0 @@
-What:		/sys/devices/cpu/events/
-		/sys/devices/cpu/events/branch-misses
-		/sys/devices/cpu/events/cache-references
-		/sys/devices/cpu/events/cache-misses
-		/sys/devices/cpu/events/stalled-cycles-frontend
-		/sys/devices/cpu/events/branch-instructions
-		/sys/devices/cpu/events/stalled-cycles-backend
-		/sys/devices/cpu/events/instructions
-		/sys/devices/cpu/events/cpu-cycles
-
-Date:		2013/01/08
-
-Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
-
-Description:	Generic performance monitoring events
-
-		A collection of performance monitoring events that may be
-		supported by many/most CPUs. These events can be monitored
-		using the 'perf(1)' tool.
-
-		The contents of each file would look like:
-
-			event=0xNNNN
-
-		where 'N' is a hex digit and the number '0xNNNN' shows the
-		"raw code" for the perf event identified by the file's
-		"basename".
-
-
-What: /sys/bus/event_source/devices/<pmu>/events/<event>
-Date: 2014/02/24
-Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
-Description:	Per-pmu performance monitoring events specific to the running system
-
-		Each file (except for some of those with a '.' in them, '.unit'
-		and '.scale') in the 'events' directory describes a single
-		performance monitoring event supported by the <pmu>. The name
-		of the file is the name of the event.
-
-		File contents:
-
-			<term>[=<value>][,<term>[=<value>]]...
-
-		Where <term> is one of the terms listed under
-		/sys/bus/event_source/devices/<pmu>/format/ and <value> is
-		a number is base-16 format with a '0x' prefix (lowercase only).
-		If a <term> is specified alone (without an assigned value), it
-		is implied that 0x1 is assigned to that <term>.
-
-		Examples (each of these lines would be in a seperate file):
-
-			event=0x2abc
-			event=0x423,inv,cmask=0x3
-			domain=0x1,offset=0x8,starting_index=0xffff
-
-		Each of the assignments indicates a value to be assigned to a
-		particular set of bits (as defined by the format file
-		corresponding to the <term>) in the perf_event structure passed
-		to the perf_open syscall.
-
-What: /sys/bus/event_source/devices/<pmu>/events/<event>.unit
-Date: 2014/02/24
-Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
-Description:	Perf event units
-
-		A string specifying the English plural numerical unit that <event>
-		(once multiplied by <event>.scale) represents.
-
-		Example:
-
-			Joules
-
-What: /sys/bus/event_source/devices/<pmu>/events/<event>.scale
-Date: 2014/02/24
-Contact:	Linux kernel mailing list <linux-kernel@vger.kernel.org>
-Description:	Perf event scaling factors
-
-		A string representing a floating point value expressed in
-		scientific notation to be multiplied by the event count
-		recieved from the kernel to match the unit specified in the
-		<event>.unit file.
-
-		Example:
-
-			2.3283064365386962890625e-10
-
-		This is provided to avoid performing floating point arithmetic
-		in the kernel.

Documentation/ABI/testing/sysfs-bus-event_source-devices-format

@@ -1,20 +0,0 @@
-Where:		/sys/bus/event_source/devices/<dev>/format
-Date:		January 2012
-Kernel Version: 3.3
-Contact:	Jiri Olsa <jolsa@redhat.com>
-Description:
-		Attribute group to describe the magic bits that go into
-		perf_event_attr::config[012] for a particular pmu.
-		Each attribute of this group defines the 'hardware' bitmask
-		we want to export, so that userspace can deal with sane
-		name/value pairs.
-
-		Userspace must be prepared for the possibility that attributes
-		define overlapping bit ranges. For example:
-			attr1 = 'config:0-23'
-			attr2 = 'config:0-7'
-			attr3 = 'config:12-35'
-
-		Example: 'config1:1,6-10,44'
-		Defines contents of attribute that occupies bits 1,6-10,44 of
-		perf_event_attr::config1.

Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_24x7

@@ -1,23 +0,0 @@
-What:		/sys/bus/event_source/devices/hv_24x7/interface/catalog
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		Provides access to the binary "24x7 catalog" provided by the
-		hypervisor on POWER7 and 8 systems. This catalog lists events
-		avaliable from the powerpc "hv_24x7" pmu. Its format is
-		documented here:
-		https://raw.githubusercontent.com/jmesmon/catalog-24x7/master/hv-24x7-catalog.h
-
-What:		/sys/bus/event_source/devices/hv_24x7/interface/catalog_length
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		A number equal to the length in bytes of the catalog. This is
-		also extractable from the provided binary "catalog" sysfs entry.
-
-What:		/sys/bus/event_source/devices/hv_24x7/interface/catalog_version
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		Exposes the "version" field of the 24x7 catalog. This is also
-		extractable from the provided binary "catalog" sysfs entry.

Documentation/ABI/testing/sysfs-bus-event_source-devices-hv_gpci

@@ -1,43 +0,0 @@
-What:		/sys/bus/event_source/devices/hv_gpci/interface/collect_privileged
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		'0' if the hypervisor is configured to forbid access to event
-		counters being accumulated by other guests and to physical
-		domain event counters.
-		'1' if that access is allowed.
-
-What:		/sys/bus/event_source/devices/hv_gpci/interface/ga
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		0 or 1. Indicates whether we have access to "GA" events (listed
-		in arch/powerpc/perf/hv-gpci.h).
-
-What:		/sys/bus/event_source/devices/hv_gpci/interface/expanded
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		0 or 1. Indicates whether we have access to "EXPANDED" events (listed
-		in arch/powerpc/perf/hv-gpci.h).
-
-What:		/sys/bus/event_source/devices/hv_gpci/interface/lab
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		0 or 1. Indicates whether we have access to "LAB" events (listed
-		in arch/powerpc/perf/hv-gpci.h).
-
-What:		/sys/bus/event_source/devices/hv_gpci/interface/version
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		A number indicating the version of the gpci interface that the
-		hypervisor reports supporting.
-
-What:		/sys/bus/event_source/devices/hv_gpci/interface/kernel_version
-Date:		February 2014
-Contact:	Linux on PowerPC Developer List <linuxppc-dev@lists.ozlabs.org>
-Description:
-		A number indicating the latest version of the gpci interface
-		that the kernel is aware of.

Documentation/ABI/testing/sysfs-bus-fcoe

@@ -1,116 +0,0 @@
-What:		/sys/bus/fcoe/
-Date:		August 2012
-KernelVersion:	TBD
-Contact:	Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
-Description:	The FCoE bus. Attributes in this directory are control interfaces.
-Attributes:
-
-	ctlr_create: 'FCoE Controller' instance creation interface. Writing an
-		     <ifname> to this file will allocate and populate sysfs with a
-		     fcoe_ctlr_device (ctlr_X). The user can then configure any
-		     per-port settings and finally write to the fcoe_ctlr_device's
-		     'start' attribute to begin the kernel's discovery and login
-		     process.
-
-	ctlr_destroy: 'FCoE Controller' instance removal interface. Writing a
-		       fcoe_ctlr_device's sysfs name to this file will log the
-		       fcoe_ctlr_device out of the fabric or otherwise connected
-		       FCoE devices. It will also free all kernel memory allocated
-		       for this fcoe_ctlr_device and any structures associated
-		       with it, this includes the scsi_host.
-
-What:		/sys/bus/fcoe/devices/ctlr_X
-Date:		March 2012
-KernelVersion:	TBD
-Contact:	Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
-Description:	'FCoE Controller' instances on the fcoe bus.
-		The FCoE Controller now has a three stage creation process.
-		1) Write interface name to ctlr_create 2) Configure the FCoE
-		Controller (ctlr_X) 3) Enable the FCoE Controller to begin
-		discovery and login. The FCoE Controller is destroyed by
-		writing it's name, i.e. ctlr_X to the ctlr_delete file.
-
-Attributes:
-
-	fcf_dev_loss_tmo: Device loss timeout peroid (see below). Changing
-			  this value will change the dev_loss_tmo for all
-			  FCFs discovered by this controller.
-
-	mode:		  Display or change the FCoE Controller's mode. Possible
-			  modes are 'Fabric' and 'VN2VN'. If a FCoE Controller
-			  is started in 'Fabric' mode then FIP FCF discovery is
-			  initiated and ultimately a fabric login is attempted.
-			  If a FCoE Controller is started in 'VN2VN' mode then
-			  FIP VN2VN discovery and login is performed. A FCoE
-			  Controller only supports one mode at a time.
-
-	enabled:	  Whether an FCoE controller is enabled or disabled.
-			  0 if disabled, 1 if enabled. Writing either 0 or 1
-			  to this file will enable or disable the FCoE controller.
-
-	lesb/link_fail:   Link Error Status Block (LESB) link failure count.
-
-	lesb/vlink_fail:  Link Error Status Block (LESB) virtual link
-			  failure count.
-
-	lesb/miss_fka:    Link Error Status Block (LESB) missed FCoE
-			  Initialization Protocol (FIP) Keep-Alives (FKA).
-
-	lesb/symb_err:    Link Error Status Block (LESB) symbolic error count.
-
-	lesb/err_block:   Link Error Status Block (LESB) block error count.
-
-	lesb/fcs_error:   Link Error Status Block (LESB) Fibre Channel
-			  Serivces error count.
-
-Notes: ctlr_X (global increment starting at 0)
-
-What:		/sys/bus/fcoe/devices/fcf_X
-Date:		March 2012
-KernelVersion:	TBD
-Contact:	Robert Love <robert.w.love@intel.com>, devel@open-fcoe.org
-Description:	'FCoE FCF' instances on the fcoe bus. A FCF is a Fibre Channel
-		Forwarder, which is a FCoE switch that can accept FCoE
-		(Ethernet) packets, unpack them, and forward the embedded
-		Fibre Channel frames into a FC fabric. It can also take
-		outbound FC frames and pack them in Ethernet packets to
-		be sent to their destination on the Ethernet segment.
-Attributes:
-
-	fabric_name: Identifies the fabric that the FCF services.
-
-	switch_name: Identifies the FCF.
-
-	priority:    The switch's priority amongst other FCFs on the same
-		     fabric.
-
-	selected:    1 indicates that the switch has been selected for use;
-		     0 indicates that the swich will not be used.
-
-	fc_map:      The Fibre Channel MAP
-
-	vfid:	     The Virtual Fabric ID
-
-	mac:         The FCF's MAC address
-
-	fka_peroid:  The FIP Keep-Alive peroid
-
-	fabric_state: The internal kernel state
-		      "Unknown" - Initialization value
-		      "Disconnected" - No link to the FCF/fabric
-		      "Connected" - Host is connected to the FCF
-		      "Deleted" - FCF is being removed from the system
-
-	dev_loss_tmo: The device loss timeout peroid for this FCF.
-
-Notes: A device loss infrastructre similar to the FC Transport's
-       is present in fcoe_sysfs. It is nice to have so that a
-       link flapping adapter doesn't continually advance the count
-       used to identify the discovered FCF. FCFs will exist in a
-       "Disconnected" state until either the timer expires and the
-       FCF becomes "Deleted" or the FCF is rediscovered and becomes
-       "Connected."
-
-
-Users: The first user of this interface will be the fcoeadm application,
-       which is commonly packaged in the fcoe-utils package.

Documentation/ABI/testing/sysfs-bus-hsi

@@ -1,19 +0,0 @@
-What:		/sys/bus/hsi
-Date:		April 2012
-KernelVersion:	3.4
-Contact:	Carlos Chinea <carlos.chinea@nokia.com>
-Description:
-		High Speed Synchronous Serial Interface (HSI) is a
-		serial interface mainly used for connecting application
-		engines (APE) with cellular modem engines (CMT) in cellular
-		handsets.
-		The bus will be populated with devices (hsi_clients) representing
-		the protocols available in the system. Bus drivers implement
-		those protocols.
-
-What:		/sys/bus/hsi/devices/.../modalias
-Date:		April 2012
-KernelVersion:	3.4
-Contact:	Carlos Chinea <carlos.chinea@nokia.com>
-Description:	Stores the same MODALIAS value emitted by uevent
-		Format: hsi:<hsi_client device name>

Documentation/ABI/testing/sysfs-bus-i2c-devices-lm3533

@@ -1,15 +0,0 @@
-What:		/sys/bus/i2c/devices/.../output_hvled[n]
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the controlling backlight device for high-voltage current
-		sink HVLED[n] (n = 1, 2) (0, 1).
-
-What:		/sys/bus/i2c/devices/.../output_lvled[n]
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the controlling led device for low-voltage current sink
-		LVLED[n] (n = 1..5) (0..3).

Documentation/ABI/testing/sysfs-bus-iio-accel-bmc150

@@ -1,7 +0,0 @@
-What:		/sys/bus/iio/devices/triggerX/name = "bmc150_accel-any-motion-devX"
-KernelVersion:	3.17
-Contact:	linux-iio@vger.kernel.org
-Description:
-		The BMC150 accelerometer kernel module provides an additional trigger,
-		which sets driver in a mode, where data is pushed to the buffer
-		only when there is any motion.

Documentation/ABI/testing/sysfs-bus-iio-frequency-ad9523

@@ -1,29 +0,0 @@
-What:		/sys/bus/iio/devices/iio:deviceX/pll2_feedback_clk_present
-What:		/sys/bus/iio/devices/iio:deviceX/pll2_reference_clk_present
-What:		/sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_a_present
-What:		/sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_b_present
-What:		/sys/bus/iio/devices/iio:deviceX/pll1_reference_clk_test_present
-What:		/sys/bus/iio/devices/iio:deviceX/vcxo_clk_present
-KernelVersion:	3.4.0
-Contact:	linux-iio@vger.kernel.org
-Description:
-		Reading returns either '1' or '0'.
-		'1' means that the clock in question is present.
-		'0' means that the clock is missing.
-
-What:		/sys/bus/iio/devices/iio:deviceX/pllY_locked
-KernelVersion:	3.4.0
-Contact:	linux-iio@vger.kernel.org
-Description:
-		Reading returns either '1' or '0'. '1' means that the
-		pllY is locked.
-
-What:		/sys/bus/iio/devices/iio:deviceX/sync_dividers
-KernelVersion:	3.4.0
-Contact:	linux-iio@vger.kernel.org
-Description:
-		Writing '1' triggers the clock distribution synchronization
-		functionality. All dividers are reset and the channels start
-		with their predefined phase offsets (out_altvoltageY_phase).
-		Writing this file has the effect as driving the external
-		/SYNC pin low.

Documentation/ABI/testing/sysfs-bus-iio-frequency-adf4350

@@ -1,21 +0,0 @@
-What:		/sys/bus/iio/devices/iio:deviceX/out_altvoltageY_frequency_resolution
-KernelVersion:	3.4.0
-Contact:	linux-iio@vger.kernel.org
-Description:
-		Stores channel Y frequency resolution/channel spacing in Hz.
-		The value given directly influences the MODULUS used by
-		the fractional-N PLL. It is assumed that the algorithm
-		that is used to compute the various dividers, is able to
-		generate proper values for multiples of channel spacing.
-
-What:		/sys/bus/iio/devices/iio:deviceX/out_altvoltageY_refin_frequency
-KernelVersion:	3.4.0
-Contact:	linux-iio@vger.kernel.org
-Description:
-		Sets channel Y REFin frequency in Hz. In some clock chained
-		applications, the reference frequency used by the PLL may
-		change during runtime. This attribute allows the user to
-		adjust the reference frequency accordingly.
-		The value written has no effect until out_altvoltageY_frequency
-		is updated. Consider to use out_altvoltageY_powerdown to power
-		down the PLL and its RFOut buffers during REFin changes.

Documentation/ABI/testing/sysfs-bus-iio-gyro-bmg160

@@ -1,7 +0,0 @@
-What:		/sys/bus/iio/devices/triggerX/name = "bmg160-any-motion-devX"
-KernelVersion:	3.17
-Contact:	linux-iio@vger.kernel.org
-Description:
-		The BMG160 gyro kernel module provides an additional trigger,
-		which sets driver in a mode, where data is pushed to the buffer
-		only when there is any motion.

Documentation/ABI/testing/sysfs-bus-iio-light-lm3533-als

@@ -1,61 +0,0 @@
-What:		/sys/.../events/in_illuminance0_thresh_either_en
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Event generated when channel passes one of the four thresholds
-		in each direction (rising|falling) and a zone change occurs.
-		The corresponding light zone can be read from
-		in_illuminance0_zone.
-
-What:		/sys/.../events/in_illuminance0_threshY_hysteresis
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Get the hysteresis for thresholds Y, that is,
-		threshY_hysteresis = threshY_raising - threshY_falling
-
-What:		/sys/.../events/illuminance_threshY_falling_value
-What:		/sys/.../events/illuminance_threshY_raising_value
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Specifies the value of threshold that the device is comparing
-		against for the events enabled by
-		in_illuminance0_thresh_either_en (0..255), where Y in 0..3.
-
-		Note that threshY_falling must be less than or equal to
-		threshY_raising.
-
-		These thresholds correspond to the eight zone-boundary
-		registers (boundaryY_{low,high}) and define the five light
-		zones.
-
-What:		/sys/bus/iio/devices/iio:deviceX/in_illuminance0_zone
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Get the current light zone (0..4) as defined by the
-		in_illuminance0_threshY_{falling,rising} thresholds.
-
-What:		/sys/bus/iio/devices/iio:deviceX/out_currentY_raw
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Get output current for channel Y (0..255), that is,
-		out_currentY_currentZ_raw, where Z is the current zone.
-
-What:		/sys/bus/iio/devices/iio:deviceX/out_currentY_currentZ_raw
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the output current for channel out_currentY when in zone
-		Z (0..255), where Y in 0..2 and Z in 0..4.
-
-		These values correspond to the ALS-mapper target registers for
-		ALS-mapper Y + 1.

Documentation/ABI/testing/sysfs-bus-iio-mpu6050

@@ -1,13 +0,0 @@
-What:           /sys/bus/iio/devices/iio:deviceX/in_gyro_matrix
-What:           /sys/bus/iio/devices/iio:deviceX/in_accel_matrix
-What:           /sys/bus/iio/devices/iio:deviceX/in_magn_matrix
-KernelVersion:  3.4.0
-Contact:        linux-iio@vger.kernel.org
-Description:
-		This is mounting matrix for motion sensors. Mounting matrix
-		is a 3x3 unitary matrix. A typical mounting matrix would look like
-		[0, 1, 0; 1, 0, 0; 0, 0, -1]. Using this information, it would be
-		easy to tell the relative positions among sensors as well as their
-		positions relative to the board that holds these sensors. Identity matrix
-		[1, 0, 0; 0, 1, 0; 0, 0, 1] means sensor chip and device are perfectly
-		aligned with each other. All axes are exactly the same.

Documentation/ABI/testing/sysfs-bus-iio-proximity-as3935

@@ -1,16 +0,0 @@
-What		/sys/bus/iio/devices/iio:deviceX/in_proximity_raw
-Date:		March 2014
-KernelVersion:	3.15
-Contact:	Matt Ranostay <mranostay@gmail.com>
-Description:
-		Get the current distance in meters of storm (1km steps)
-		1000-40000 = distance in meters
-
-What		/sys/bus/iio/devices/iio:deviceX/sensor_sensitivity
-Date:		March 2014
-KernelVersion:	3.15
-Contact:	Matt Ranostay <mranostay@gmail.com>
-Description:
-		Show or set the gain boost of the amp, from 0-31 range.
-		18 = indoors (default)
-		14 = outdoors

Documentation/ABI/testing/sysfs-bus-mdio

@@ -1,29 +0,0 @@
-What:		/sys/bus/mdio_bus/devices/.../phy_id
-Date:		November 2012
-KernelVersion:	3.8
-Contact:	netdev@vger.kernel.org
-Description:
-		This attribute contains the 32-bit PHY Identifier as reported
-		by the device during bus enumeration, encoded in hexadecimal.
-		This ID is used to match the device with the appropriate
-		driver.
-
-What:		/sys/bus/mdio_bus/devices/.../phy_interface
-Date:		February 2014
-KernelVersion:	3.15
-Contact:	netdev@vger.kernel.org
-Description:
-		This attribute contains the PHY interface as configured by the
-		Ethernet driver during bus enumeration, encoded in string.
-		This interface mode is used to configure the Ethernet MAC with the
-		appropriate mode for its data lines to the PHY hardware.
-
-What:		/sys/bus/mdio_bus/devices/.../phy_has_fixups
-Date:		February 2014
-KernelVersion:	3.15
-Contact:	netdev@vger.kernel.org
-Description:
-		This attribute contains the boolean value whether a given PHY
-		device has had any "fixup" workaround running on it, encoded as
-		a boolean. This information is provided to help troubleshooting
-		PHY configurations.

Documentation/ABI/testing/sysfs-bus-mei

@@ -1,7 +0,0 @@
-What:		/sys/bus/mei/devices/.../modalias
-Date:		March 2013
-KernelVersion:	3.10
-Contact:	Samuel Ortiz <sameo@linux.intel.com>
-		linux-mei@linux.intel.com
-Description:	Stores the same MODALIAS value emitted by uevent
-		Format: mei:<mei device name>

Documentation/ABI/testing/sysfs-bus-pci

@@ -64,31 +64,7 @@ Description:
 		Writing a non-zero value to this attribute will
 		force a rescan of all PCI buses in the system, and
 		re-discover previously removed devices.
-
-What:		/sys/bus/pci/devices/.../msi_bus
-Date:		September 2014
-Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
-Description:
-		Writing a zero value to this attribute disallows MSI and
-		MSI-X for any future drivers of the device.  If the device
-		is a bridge, MSI and MSI-X will be disallowed for future
-		drivers of all child devices under the bridge.  Drivers
-		must be reloaded for the new setting to take effect.
-
-What:		/sys/bus/pci/devices/.../msi_irqs/
-Date:		September, 2011
-Contact:	Neil Horman <nhorman@tuxdriver.com>
-Description:
-		The /sys/devices/.../msi_irqs directory contains a variable set
-		of files, with each file being named after a corresponding msi
-		irq vector allocated to that device.
-
-What:		/sys/bus/pci/devices/.../msi_irqs/<N>
-Date:		September 2011
-Contact:	Neil Horman <nhorman@tuxdriver.com>
-Description:
-		This attribute indicates the mode that the irq vector named by
-		the file is in (msi vs. msix)
+		Depends on CONFIG_HOTPLUG.
 
 What:		/sys/bus/pci/devices/.../remove
 Date:		January 2009
@@ -96,6 +72,7 @@ Contact:	Linux PCI developers <linux-pci@vger.kernel.org>
 Description:
 		Writing a non-zero value to this attribute will
 		hot-remove the PCI device and any of its children.
+		Depends on CONFIG_HOTPLUG.
 
 What:		/sys/bus/pci/devices/.../pci_bus/.../rescan
 Date:		May 2011
@@ -104,7 +81,7 @@ Description:
 		Writing a non-zero value to this attribute will
 		force a rescan of the bus and all child buses,
 		and re-discover devices removed earlier from this
-		part of the device tree.
+		part of the device tree.  Depends on CONFIG_HOTPLUG.
 
 What:		/sys/bus/pci/devices/.../rescan
 Date:		January 2009
@@ -114,6 +91,7 @@ Description:
 		force a rescan of the device's parent bus and all
 		child buses, and re-discover devices removed earlier
 		from this part of the device tree.
+		Depends on CONFIG_HOTPLUG.
 
 What:		/sys/bus/pci/devices/.../reset
 Date:		July 2009
@@ -127,7 +105,7 @@ Description:
 
 What:		/sys/bus/pci/devices/.../vpd
 Date:		February 2008
-Contact:	Ben Hutchings <bwh@kernel.org>
+Contact:	Ben Hutchings <bhutchings@solarflare.com>
 Description:
 		A file named vpd in a device directory will be a
 		binary file containing the Vital Product Data for the
@@ -214,70 +192,3 @@ Users:
 		firmware assigned instance number of the PCI
 		device that can help in understanding the firmware
 		intended order of the PCI device.
-
-What:		/sys/bus/pci/devices/.../d3cold_allowed
-Date:		July 2012
-Contact:	Huang Ying <ying.huang@intel.com>
-Description:
-		d3cold_allowed is bit to control whether the corresponding PCI
-		device can be put into D3Cold state.  If it is cleared, the
-		device will never be put into D3Cold state.  If it is set, the
-		device may be put into D3Cold state if other requirements are
-		satisfied too.  Reading this attribute will show the current
-		value of d3cold_allowed bit.  Writing this attribute will set
-		the value of d3cold_allowed bit.
-
-What:		/sys/bus/pci/devices/.../sriov_totalvfs
-Date:		November 2012
-Contact:	Donald Dutile <ddutile@redhat.com>
-Description:
-		This file appears when a physical PCIe device supports SR-IOV.
-		Userspace applications can read this file to determine the
-		maximum number of Virtual Functions (VFs) a PCIe physical
-		function (PF) can support. Typically, this is the value reported
-		in the PF's SR-IOV extended capability structure's TotalVFs
-		element.  Drivers have the ability at probe time to reduce the
-		value read from this file via the pci_sriov_set_totalvfs()
-		function.
-
-What:		/sys/bus/pci/devices/.../sriov_numvfs
-Date:		November 2012
-Contact:	Donald Dutile <ddutile@redhat.com>
-Description:
-		This file appears when a physical PCIe device supports SR-IOV.
-		Userspace applications can read and write to this file to
-		determine and control the enablement or disablement of Virtual
-		Functions (VFs) on the physical function (PF). A read of this
-		file will return the number of VFs that are enabled on this PF.
-		A number written to this file will enable the specified
-		number of VFs. A userspace application would typically read the
-		file and check that the value is zero, and then write the number
-		of VFs that should be enabled on the PF; the value written
-		should be less than or equal to the value in the sriov_totalvfs
-		file. A userspace application wanting to disable the VFs would
-		write a zero to this file. The core ensures that valid values
-		are written to this file, and returns errors when values are not
-		valid.  For example, writing a 2 to this file when sriov_numvfs
-		is not 0 and not 2 already will return an error. Writing a 10
-		when the value of sriov_totalvfs is 8 will return an error.
-
-What:		/sys/bus/pci/devices/.../driver_override
-Date:		April 2014
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		This file allows the driver for a device to be specified which
-		will override standard static and dynamic ID matching.  When
-		specified, only a driver with a name matching the value written
-		to driver_override will have an opportunity to bind to the
-		device.  The override is specified by writing a string to the
-		driver_override file (echo pci-stub > driver_override) and
-		may be cleared with an empty string (echo > driver_override).
-		This returns the device to standard matching rules binding.
-		Writing to driver_override does not automatically unbind the
-		device from its current driver or make any attempt to
-		automatically load the specified driver.  If no driver with a
-		matching name is currently loaded in the kernel, the device
-		will not bind to any driver.  This also allows devices to
-		opt-out of driver binding using a driver_override name such as
-		"none".  Only a single driver may be specified in the override,
-		there is no support for parsing delimiters.

Documentation/ABI/testing/sysfs-bus-platform

@@ -1,20 +0,0 @@
-What:		/sys/bus/platform/devices/.../driver_override
-Date:		April 2014
-Contact:	Kim Phillips <kim.phillips@freescale.com>
-Description:
-		This file allows the driver for a device to be specified which
-		will override standard OF, ACPI, ID table, and name matching.
-		When specified, only a driver with a name matching the value
-		written to driver_override will have an opportunity to bind
-		to the device.  The override is specified by writing a string
-		to the driver_override file (echo vfio-platform > \
-		driver_override) and may be cleared with an empty string
-		(echo > driver_override).  This returns the device to standard
-		matching rules binding.  Writing to driver_override does not
-		automatically unbind the device from its current driver or make
-		any attempt to automatically load the specified driver.  If no
-		driver with a matching name is currently loaded in the kernel,
-		the device will not bind to any driver.  This also allows
-		devices to opt-out of driver binding using a driver_override
-		name such as "none".  Only a single driver may be specified in
-		the override, there is no support for parsing delimiters.

Documentation/ABI/testing/sysfs-bus-rbd

@@ -18,28 +18,6 @@ Removal of a device:
 
   $ echo <dev-id> > /sys/bus/rbd/remove
 
-What:		/sys/bus/rbd/add_single_major
-Date:		December 2013
-KernelVersion:	3.14
-Contact:	Sage Weil <sage@inktank.com>
-Description:	Available only if rbd module is inserted with single_major
-		parameter set to true.
-		Usage is the same as for /sys/bus/rbd/add.  If present,
-		should be used instead of the latter: any attempts to use
-		/sys/bus/rbd/add if /sys/bus/rbd/add_single_major is
-		available will fail for backwards compatibility reasons.
-
-What:		/sys/bus/rbd/remove_single_major
-Date:		December 2013
-KernelVersion:	3.14
-Contact:	Sage Weil <sage@inktank.com>
-Description:	Available only if rbd module is inserted with single_major
-		parameter set to true.
-		Usage is the same as for /sys/bus/rbd/remove.  If present,
-		should be used instead of the latter: any attempts to use
-		/sys/bus/rbd/remove if /sys/bus/rbd/remove_single_major is
-		available will fail for backwards compatibility reasons.
-
 Entries under /sys/bus/rbd/devices/<dev-id>/
 --------------------------------------------
 
@@ -47,37 +25,18 @@ client_id
 
 	The ceph unique client id that was assigned for this specific session.
 
-features
-
-	A hexadecimal encoding of the feature bits for this image.
-
 major
 
 	The block device major number.
 
-minor
-
-	The block device minor number.  (December 2013, since 3.14.)
-
 name
 
 	The name of the rbd image.
 
-image_id
-
-	The unique id for the rbd image.  (For rbd image format 1
-	this is empty.)
-
 pool
 
-	The name of the storage pool where this rbd image resides.
-	An rbd image name is unique within its pool.
-
-pool_id
-
-	The unique identifier for the rbd image's pool.  This is
-	a permanent attribute of the pool.  A pool's id will never
-	change.
+	The pool where this rbd image resides. The pool-name pair is unique
+	per rados system.
 
 size
 
@@ -92,7 +51,26 @@ current_snap
 
 	The current snapshot for which the device is mapped.
 
-parent
+create_snap
+
+	Create a snapshot:
+
+	 $ echo <snap-name> > /sys/bus/rbd/devices/<dev-id>/snap_create
+
+snap_*
+
+	A directory per each snapshot
+
+
+Entries under /sys/bus/rbd/devices/<dev-id>/snap_<snap-name>
+-------------------------------------------------------------
+
+id
+
+	The rados internal snapshot id assigned for this snapshot
+
+size
+
+	The size of the image when this snapshot was taken.
+
 
-	Information identifying the chain of parent images in a layered rbd
-	image.  Entries are separated by empty lines.

Documentation/ABI/testing/sysfs-bus-rpmsg

@@ -1,75 +0,0 @@
-What:		/sys/bus/rpmsg/devices/.../name
-Date:		June 2011
-KernelVersion:	3.3
-Contact:	Ohad Ben-Cohen <ohad@wizery.com>
-Description:
-		Every rpmsg device is a communication channel with a remote
-		processor. Channels are identified with a (textual) name,
-		which is maximum 32 bytes long (defined as RPMSG_NAME_SIZE in
-		rpmsg.h).
-
-		This sysfs entry contains the name of this channel.
-
-What:		/sys/bus/rpmsg/devices/.../src
-Date:		June 2011
-KernelVersion:	3.3
-Contact:	Ohad Ben-Cohen <ohad@wizery.com>
-Description:
-		Every rpmsg device is a communication channel with a remote
-		processor. Channels have a local ("source") rpmsg address,
-		and remote ("destination") rpmsg address. When an entity
-		starts listening on one end of a channel, it assigns it with
-		a unique rpmsg address (a 32 bits integer). This way when
-		inbound messages arrive to this address, the rpmsg core
-		dispatches them to the listening entity (a kernel driver).
-
-		This sysfs entry contains the src (local) rpmsg address
-		of this channel. If it contains 0xffffffff, then an address
-		wasn't assigned (can happen if no driver exists for this
-		channel).
-
-What:		/sys/bus/rpmsg/devices/.../dst
-Date:		June 2011
-KernelVersion:	3.3
-Contact:	Ohad Ben-Cohen <ohad@wizery.com>
-Description:
-		Every rpmsg device is a communication channel with a remote
-		processor. Channels have a local ("source") rpmsg address,
-		and remote ("destination") rpmsg address. When an entity
-		starts listening on one end of a channel, it assigns it with
-		a unique rpmsg address (a 32 bits integer). This way when
-		inbound messages arrive to this address, the rpmsg core
-		dispatches them to the listening entity.
-
-		This sysfs entry contains the dst (remote) rpmsg address
-		of this channel. If it contains 0xffffffff, then an address
-		wasn't assigned (can happen if the kernel driver that
-		is attached to this channel is exposing a service to the
-		remote processor. This make it a local rpmsg server,
-		and it is listening for inbound messages that may be sent
-		from any remote rpmsg client; it is not bound to a single
-		remote entity).
-
-What:		/sys/bus/rpmsg/devices/.../announce
-Date:		June 2011
-KernelVersion:	3.3
-Contact:	Ohad Ben-Cohen <ohad@wizery.com>
-Description:
-		Every rpmsg device is a communication channel with a remote
-		processor. Channels are identified by a textual name (see
-		/sys/bus/rpmsg/devices/.../name above) and have a local
-		("source") rpmsg address, and remote ("destination") rpmsg
-		address.
-
-		A channel is first created when an entity, whether local
-		or remote, starts listening on it for messages (and is thus
-		called an rpmsg server).
-
-		When that happens, a "name service" announcement is sent
-		to the other processor, in order to let it know about the
-		creation of the channel (this way remote clients know they
-		can start sending messages).
-
-		This sysfs entry tells us whether the channel is a local
-		server channel that is announced (values are either
-		true or false).

Documentation/ABI/testing/sysfs-bus-usb

@@ -1,3 +1,81 @@
+What:		/sys/bus/usb/devices/.../power/autosuspend
+Date:		March 2007
+KernelVersion:	2.6.21
+Contact:	Alan Stern <stern@rowland.harvard.edu>
+Description:
+		Each USB device directory will contain a file named
+		power/autosuspend.  This file holds the time (in seconds)
+		the device must be idle before it will be autosuspended.
+		0 means the device will be autosuspended as soon as
+		possible.  Negative values will prevent the device from
+		being autosuspended at all, and writing a negative value
+		will resume the device if it is already suspended.
+
+		The autosuspend delay for newly-created devices is set to
+		the value of the usbcore.autosuspend module parameter.
+
+What:		/sys/bus/usb/devices/.../power/persist
+Date:		May 2007
+KernelVersion:	2.6.23
+Contact:	Alan Stern <stern@rowland.harvard.edu>
+Description:
+		If CONFIG_USB_PERSIST is set, then each USB device directory
+		will contain a file named power/persist.  The file holds a
+		boolean value (0 or 1) indicating whether or not the
+		"USB-Persist" facility is enabled for the device.  Since the
+		facility is inherently dangerous, it is disabled by default
+		for all devices except hubs.  For more information, see
+		Documentation/usb/persist.txt.
+
+What:		/sys/bus/usb/device/.../power/connected_duration
+Date:		January 2008
+KernelVersion:	2.6.25
+Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
+Description:
+		If CONFIG_PM and CONFIG_USB_SUSPEND are enabled, then this file
+		is present.  When read, it returns the total time (in msec)
+		that the USB device has been connected to the machine.  This
+		file is read-only.
+Users:
+		PowerTOP <power@bughost.org>
+		http://www.lesswatts.org/projects/powertop/
+
+What:		/sys/bus/usb/device/.../power/active_duration
+Date:		January 2008
+KernelVersion:	2.6.25
+Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
+Description:
+		If CONFIG_PM and CONFIG_USB_SUSPEND are enabled, then this file
+		is present.  When read, it returns the total time (in msec)
+		that the USB device has been active, i.e. not in a suspended
+		state.  This file is read-only.
+
+		Tools can use this file and the connected_duration file to
+		compute the percentage of time that a device has been active.
+		For example,
+		echo $((100 * `cat active_duration` / `cat connected_duration`))
+		will give an integer percentage.  Note that this does not
+		account for counter wrap.
+Users:
+		PowerTOP <power@bughost.org>
+		http://www.lesswatts.org/projects/powertop/
+
+What:		/sys/bus/usb/device/<busnum>-<devnum>...:<config num>-<interface num>/supports_autosuspend
+Date:		January 2008
+KernelVersion:	2.6.27
+Contact:	Sarah Sharp <sarah.a.sharp@intel.com>
+Description:
+		When read, this file returns 1 if the interface driver
+		for this interface supports autosuspend.  It also
+		returns 1 if no driver has claimed this interface, as an
+		unclaimed interface will not stop the device from being
+		autosuspended if all other interface drivers are idle.
+		The file returns 0 if autosuspend support has not been
+		added to the driver.
+Users:
+		USB PM tool
+		git://git.moblin.org/users/sarah/usb-pm-tool/
+
 What:		/sys/bus/usb/device/.../authorized
 Date:		July 2008
 KernelVersion:	2.6.26
@@ -41,48 +119,6 @@ Description:
 		Write a 1 to force the device to disconnect
 		(equivalent to unplugging a wired USB device).
 
-What:		/sys/bus/usb/drivers/.../new_id
-Date:		October 2011
-Contact:	linux-usb@vger.kernel.org
-Description:
-		Writing a device ID to this file will attempt to
-		dynamically add a new device ID to a USB device driver.
-		This may allow the driver to support more hardware than
-		was included in the driver's static device ID support
-		table at compile time. The format for the device ID is:
-		idVendor idProduct bInterfaceClass RefIdVendor RefIdProduct
-		The vendor ID and device ID fields are required, the
-		rest is optional. The Ref* tuple can be used to tell the
-		driver to use the same driver_data for the new device as
-		it is used for the reference device.
-		Upon successfully adding an ID, the driver will probe
-		for the device and attempt to bind to it.  For example:
-		# echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
-
-		Here add a new device (0458:7045) using driver_data from
-		an already supported device (0458:704c):
-		# echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
-
-		Reading from this file will list all dynamically added
-		device IDs in the same format, with one entry per
-		line. For example:
-		# cat /sys/bus/usb/drivers/foo/new_id
-		8086 10f5
-		dead beef 06
-		f00d cafe
-
-		The list will be truncated at PAGE_SIZE bytes due to
-		sysfs restrictions.
-
-What:		/sys/bus/usb-serial/drivers/.../new_id
-Date:		October 2011
-Contact:	linux-usb@vger.kernel.org
-Description:
-		For serial USB drivers, this attribute appears under the
-		extra bus folder "usb-serial" in sysfs; apart from that
-		difference, all descriptions from the entry
-		"/sys/bus/usb/drivers/.../new_id" apply.
-
 What:		/sys/bus/usb/drivers/.../remove_id
 Date:		November 2009
 Contact:	CHENG Renquan <rqcheng@smu.edu.sg>
@@ -96,15 +132,22 @@ Description:
 		match the driver to the device.  For example:
 		# echo "046d c315" > /sys/bus/usb/drivers/foo/remove_id
 
-		Reading from this file will list the dynamically added
-		device IDs, exactly like reading from the entry
-		"/sys/bus/usb/drivers/.../new_id"
+What:		/sys/bus/usb/device/.../avoid_reset_quirk
+Date:		December 2009
+Contact:	Oliver Neukum <oliver@neukum.org>
+Description:
+		Writing 1 to this file tells the kernel that this
+		device will morph into another mode when it is reset.
+		Drivers will not use reset for error handling for
+		such devices.
+Users:
+		usb_modeswitch
 
 What:		/sys/bus/usb/devices/.../power/usb2_hardware_lpm
 Date:		September 2011
 Contact:	Andiry Xu <andiry.xu@amd.com>
 Description:
-		If CONFIG_PM_RUNTIME is set and a USB 2.0 lpm-capable device
+		If CONFIG_USB_SUSPEND is set and a USB 2.0 lpm-capable device
 		is plugged in to a xHCI host which support link PM, it will
 		perform a LPM test; if the test is passed and host supports
 		USB2 hardware LPM (xHCI 1.0 feature), USB2 hardware LPM will
@@ -114,69 +157,3 @@ Description:
 		USB2 hardware LPM is enabled for the device. Developer can
 		write y/Y/1 or n/N/0 to the file to enable/disable the
 		feature.
-
-What:		/sys/bus/usb/devices/.../removable
-Date:		February 2012
-Contact:	Matthew Garrett <mjg@redhat.com>
-Description:
-		Some information about whether a given USB device is
-		physically fixed to the platform can be inferred from a
-		combination of hub descriptor bits and platform-specific data
-		such as ACPI. This file will read either "removable" or
-		"fixed" if the information is available, and "unknown"
-		otherwise.
-
-What:		/sys/bus/usb/devices/.../ltm_capable
-Date:		July 2012
-Contact:	Sarah Sharp <sarah.a.sharp@linux.intel.com>
-Description:
-		USB 3.0 devices may optionally support Latency Tolerance
-		Messaging (LTM).  They indicate their support by setting a bit
-		in the bmAttributes field of their SuperSpeed BOS descriptors.
-		If that bit is set for the device, ltm_capable will read "yes".
-		If the device doesn't support LTM, the file will read "no".
-		The file will be present for all speeds of USB devices, and will
-		always read "no" for USB 1.1 and USB 2.0 devices.
-
-What:		/sys/bus/usb/devices/.../(hub interface)/portX
-Date:		August 2012
-Contact:	Lan Tianyu <tianyu.lan@intel.com>
-Description:
-		The /sys/bus/usb/devices/.../(hub interface)/portX
-		is usb port device's sysfs directory.
-
-What:		/sys/bus/usb/devices/.../(hub interface)/portX/connect_type
-Date:		January 2013
-Contact:	Lan Tianyu <tianyu.lan@intel.com>
-Description:
-		Some platforms provide usb port connect types through ACPI.
-		This attribute is to expose these information to user space.
-		The file will read "hotplug", "wired" and "not used" if the
-		information is available, and "unknown" otherwise.
-
-What:		/sys/bus/usb/devices/.../power/usb2_lpm_l1_timeout
-Date:		May 2013
-Contact:	Mathias Nyman <mathias.nyman@linux.intel.com>
-Description:
-		USB 2.0 devices may support hardware link power management (LPM)
-		L1 sleep state. The usb2_lpm_l1_timeout attribute allows
-		tuning the timeout for L1 inactivity timer (LPM timer), e.g.
-		needed inactivity time before host requests the device to go to L1 sleep.
-		Useful for power management tuning.
-		Supported values are 0 - 65535 microseconds.
-
-What:		/sys/bus/usb/devices/.../power/usb2_lpm_besl
-Date:		May 2013
-Contact:	Mathias Nyman <mathias.nyman@linux.intel.com>
-Description:
-		USB 2.0 devices that support hardware link power management (LPM)
-		L1 sleep state now use a best effort service latency value (BESL) to
-		indicate the best effort to resumption of service to the device after the
-		initiation of the resume event.
-		If the device does not have a preferred besl value then the host can select
-		one instead. This usb2_lpm_besl attribute allows to tune the host selected besl
-		value in order to tune power saving and service latency.
-
-		Supported values are 0 - 15.
-		More information on how besl values map to microseconds can be found in
-		USB 2.0 ECN Errata for Link Power Management, section 4.10)

Documentation/ABI/testing/sysfs-bus-usb-devices-usbsevseg

@@ -40,4 +40,4 @@ Description:	Controls the decimal places on the device.
 		the value of 10 ** n. Assume this field has
 		the value k and has 1 or more decimal places set,
 		to set the mth place (where m is not already set),
-		change this fields value to k + 10 ** m.
+		change this fields value to k + 10 ** m.

Documentation/ABI/testing/sysfs-bus-usb-lvstest

@@ -1,47 +0,0 @@
-Link Layer Validation Device is a standard device for testing of Super
-Speed Link Layer tests. These nodes are available in sysfs only when lvs
-driver is bound with root hub device.
-
-What:		/sys/bus/usb/devices/.../get_dev_desc
-Date:		March 2014
-Contact:	Pratyush Anand <pratyush.anand@st.com>
-Description:
-		Write to this node to issue "Get Device Descriptor"
-		for Link Layer Validation device. It is needed for TD.7.06.
-
-What:		/sys/bus/usb/devices/.../u1_timeout
-Date:		March 2014
-Contact:	Pratyush Anand <pratyush.anand@st.com>
-Description:
-		Set "U1 timeout" for the downstream port where Link Layer
-		Validation device is connected. Timeout value must be between 0
-		and 127. It is needed for TD.7.18, TD.7.19, TD.7.20 and TD.7.21.
-
-What:		/sys/bus/usb/devices/.../u2_timeout
-Date:		March 2014
-Contact:	Pratyush Anand <pratyush.anand@st.com>
-Description:
-		Set "U2 timeout" for the downstream port where Link Layer
-		Validation device is connected. Timeout value must be between 0
-		and 127. It is needed for TD.7.18, TD.7.19, TD.7.20 and TD.7.21.
-
-What:		/sys/bus/usb/devices/.../hot_reset
-Date:		March 2014
-Contact:	Pratyush Anand <pratyush.anand@st.com>
-Description:
-		Write to this node to issue "Reset" for Link Layer Validation
-		device. It is needed for TD.7.29, TD.7.31, TD.7.34 and TD.7.35.
-
-What:		/sys/bus/usb/devices/.../u3_entry
-Date:		March 2014
-Contact:	Pratyush Anand <pratyush.anand@st.com>
-Description:
-		Write to this node to issue "U3 entry" for Link Layer
-		Validation device. It is needed for TD.7.35 and TD.7.36.
-
-What:		/sys/bus/usb/devices/.../u3_exit
-Date:		March 2014
-Contact:	Pratyush Anand <pratyush.anand@st.com>
-Description:
-		Write to this node to issue "U3 exit" for Link Layer
-		Validation device. It is needed for TD.7.36.

Documentation/ABI/testing/sysfs-cfq-target-latency

@@ -1,8 +0,0 @@
-What:		/sys/block/<device>/iosched/target_latency
-Date:		March 2012
-contact:	Tao Ma <boyu.mt@taobao.com>
-Description:
-		The /sys/block/<device>/iosched/target_latency only exists
-		when the user sets cfq to /sys/block/<device>/scheduler.
-		It contains an estimated latency time for the cfq. cfq will
-		use it to calculate the time slice used for every task.

Documentation/ABI/testing/sysfs-class

@@ -1,6 +1,6 @@
 What:		/sys/class/
 Date:		Febuary 2006
-Contact:	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+Contact:	Greg Kroah-Hartman <gregkh@suse.de>
 Description:
 		The /sys/class directory will consist of a group of
 		subdirectories describing individual classes of devices

Documentation/ABI/testing/sysfs-class-backlight-driver-adp8870

@@ -53,4 +53,4 @@ Description:
 		Documentation/ABI/stable/sysfs-class-backlight.
 		It can be enabled by writing the value stored in
 		/sys/class/backlight/<backlight>/max_brightness to
-		/sys/class/backlight/<backlight>/brightness.
+		/sys/class/backlight/<backlight>/brightness.

Documentation/ABI/testing/sysfs-class-backlight-driver-lm3533

@@ -1,48 +0,0 @@
-What:		/sys/class/backlight/<backlight>/als_channel
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Get the ALS output channel used as input in
-		ALS-current-control mode (0, 1), where
-
-		0 - out_current0 (backlight 0)
-		1 - out_current1 (backlight 1)
-
-What:		/sys/class/backlight/<backlight>/als_en
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Enable ALS-current-control mode (0, 1).
-
-What:		/sys/class/backlight/<backlight>/id
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Get the id of this backlight (0, 1).
-
-What:		/sys/class/backlight/<backlight>/linear
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the brightness-mapping mode (0, 1), where
-
-		0 - exponential mode
-		1 - linear mode
-
-What:		/sys/class/backlight/<backlight>/pwm
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the PWM-input control mask (5 bits), where
-
-		bit 5 - PWM-input enabled in Zone 4
-		bit 4 - PWM-input enabled in Zone 3
-		bit 3 - PWM-input enabled in Zone 2
-		bit 2 - PWM-input enabled in Zone 1
-		bit 1 - PWM-input enabled in Zone 0
-		bit 0 - PWM-input enabled

Documentation/ABI/testing/sysfs-class-bdi

@@ -48,8 +48,3 @@ max_ratio (read-write)
 	most of the write-back cache.  For example in case of an NFS
 	mount that is prone to get stuck, or a FUSE mount which cannot
 	be trusted to play fair.
-
-stable_pages_required (read-only)
-
-	If set, the backing device requires that all pages comprising a write
-	request must not be changed until writeout is complete.

Documentation/ABI/testing/sysfs-class-cxl

@@ -1,129 +0,0 @@
-Slave contexts (eg. /sys/class/cxl/afu0.0s):
-
-What:           /sys/class/cxl/<afu>/irqs_max
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read/write
-                Decimal value of maximum number of interrupts that can be
-                requested by userspace.  The default on probe is the maximum
-                that hardware can support (eg. 2037). Write values will limit
-                userspace applications to that many userspace interrupts. Must
-                be >= irqs_min.
-
-What:           /sys/class/cxl/<afu>/irqs_min
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the minimum number of interrupts that
-                userspace must request on a CXL_START_WORK ioctl. Userspace may
-                omit the num_interrupts field in the START_WORK IOCTL to get
-                this minimum automatically.
-
-What:           /sys/class/cxl/<afu>/mmio_size
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the size of the MMIO space that may be mmaped
-                by userspace.
-
-What:           /sys/class/cxl/<afu>/modes_supported
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                List of the modes this AFU supports. One per line.
-                Valid entries are: "dedicated_process" and "afu_directed"
-
-What:           /sys/class/cxl/<afu>/mode
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read/write
-                The current mode the AFU is using. Will be one of the modes
-                given in modes_supported. Writing will change the mode
-                provided that no user contexts are attached.
-
-
-What:           /sys/class/cxl/<afu>/prefault_mode
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read/write
-                Set the mode for prefaulting in segments into the segment table
-                when performing the START_WORK ioctl. Possible values:
-                        none: No prefaulting (default)
-                        work_element_descriptor: Treat the work element
-                                 descriptor as an effective address and
-                                 prefault what it points to.
-                        all: all segments process calling START_WORK maps.
-
-What:           /sys/class/cxl/<afu>/reset
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    write only
-                Writing 1 here will reset the AFU provided there are not
-                contexts active on the AFU.
-
-What:           /sys/class/cxl/<afu>/api_version
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the current version of the kernel/user API.
-
-What:           /sys/class/cxl/<afu>/api_version_com
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the the lowest version of the userspace API
-                this this kernel supports.
-
-
-
-Master contexts (eg. /sys/class/cxl/afu0.0m)
-
-What:           /sys/class/cxl/<afu>m/mmio_size
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the size of the MMIO space that may be mmaped
-                by userspace. This includes all slave contexts space also.
-
-What:           /sys/class/cxl/<afu>m/pp_mmio_len
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the Per Process MMIO space length.
-
-What:           /sys/class/cxl/<afu>m/pp_mmio_off
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Decimal value of the Per Process MMIO space offset.
-
-
-Card info (eg. /sys/class/cxl/card0)
-
-What:           /sys/class/cxl/<card>/caia_version
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Identifies the CAIA Version the card implements.
-
-What:           /sys/class/cxl/<card>/psl_version
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Identifies the revision level of the PSL.
-
-What:           /sys/class/cxl/<card>/base_image
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Identifies the revision level of the base image for devices
-                that support loadable PSLs. For FPGAs this field identifies
-                the image contained in the on-adapter flash which is loaded
-                during the initial program load.
-
-What:           /sys/class/cxl/<card>/image_loaded
-Date:           September 2014
-Contact:        linuxppc-dev@lists.ozlabs.org
-Description:    read only
-                Will return "user" or "factory" depending on the image loaded
-                onto the card.

Documentation/ABI/testing/sysfs-class-devfreq

@@ -11,7 +11,7 @@ What:		/sys/class/devfreq/.../governor
 Date:		September 2011
 Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
 Description:
-		The /sys/class/devfreq/.../governor show or set the name of the
+		The /sys/class/devfreq/.../governor shows the name of the
 		governor used by the corresponding devfreq object.
 
 What:		/sys/class/devfreq/.../cur_freq
@@ -19,16 +19,15 @@ Date:		September 2011
 Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
 Description:
 		The /sys/class/devfreq/.../cur_freq shows the current
-		frequency of the corresponding devfreq object. Same as
-		target_freq when get_cur_freq() is not implemented by
-		devfreq driver.
+		frequency of the corresponding devfreq object.
 
-What:		/sys/class/devfreq/.../target_freq
-Date:		September 2012
-Contact:	Rajagopal Venkat <rajagopal.venkat@linaro.org>
+What:		/sys/class/devfreq/.../central_polling
+Date:		September 2011
+Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
 Description:
-		The /sys/class/devfreq/.../target_freq shows the next governor
-		predicted target frequency of the corresponding devfreq object.
+		The /sys/class/devfreq/.../central_polling shows whether
+		the devfreq ojbect is using devfreq-provided central
+		polling mechanism or not.
 
 What:		/sys/class/devfreq/.../polling_interval
 Date:		September 2011
@@ -44,17 +43,6 @@ Description:
 		(/sys/class/devfreq/.../central_polling is 0), this value
 		may be useless.
 
-What:		/sys/class/devfreq/.../trans_stat
-Date:		October 2012
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Descrtiption:
-		This ABI shows the statistics of devfreq behavior on a
-		specific device. It shows the time spent in each state and
-		the number of transitions between states.
-		In order to activate this ABI, the devfreq target device
-		driver should provide the list of available frequencies
-		with its profile.
-
 What:		/sys/class/devfreq/.../userspace/set_freq
 Date:		September 2011
 Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
@@ -62,39 +50,3 @@ Description:
 		The /sys/class/devfreq/.../userspace/set_freq shows and
 		sets the requested frequency for the devfreq object if
 		userspace governor is in effect.
-
-What:		/sys/class/devfreq/.../available_frequencies
-Date:		October 2012
-Contact:	Nishanth Menon <nm@ti.com>
-Description:
-		The /sys/class/devfreq/.../available_frequencies shows
-		the available frequencies of the corresponding devfreq object.
-		This is a snapshot of available frequencies and not limited
-		by the min/max frequency restrictions.
-
-What:		/sys/class/devfreq/.../available_governors
-Date:		October 2012
-Contact:	Nishanth Menon <nm@ti.com>
-Description:
-		The /sys/class/devfreq/.../available_governors shows
-		currently available governors in the system.
-
-What:		/sys/class/devfreq/.../min_freq
-Date:		January 2013
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		The /sys/class/devfreq/.../min_freq shows and stores
-		the minimum frequency requested by users. It is 0 if
-		the user does not care. min_freq overrides the
-		frequency requested by governors.
-
-What:		/sys/class/devfreq/.../max_freq
-Date:		January 2013
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		The /sys/class/devfreq/.../max_freq shows and stores
-		the maximum frequency requested by users. It is 0 if
-		the user does not care. max_freq overrides the
-		frequency requested by governors and min_freq.
-		The max_freq overrides min_freq because max_freq may be
-		used to throttle devices to avoid overheating.

Documentation/ABI/testing/sysfs-class-extcon

@@ -1,97 +0,0 @@
-What:		/sys/class/extcon/.../
-Date:		February 2012
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		Provide a place in sysfs for the extcon objects.
-		This allows accessing extcon specific variables.
-		The name of extcon object denoted as ... is the name given
-		with extcon_dev_register.
-
-		One extcon device denotes a single external connector
-		port. An external connector may have multiple cables
-		attached simultaneously. Many of docks, cradles, and
-		accessory cables have such capability. For example,
-		the 30-pin port of Nuri board (/arch/arm/mach-exynos)
-		may have both HDMI and Charger attached, or analog audio,
-		video, and USB cables attached simultaneously.
-
-		If there are cables mutually exclusive with each other,
-		such binary relations may be expressed with extcon_dev's
-		mutually_exclusive array.
-
-What:		/sys/class/extcon/.../name
-Date:		February 2012
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		The /sys/class/extcon/.../name shows the name of the extcon
-		object. If the extcon object has an optional callback
-		"show_name" defined, the callback will provide the name with
-		this sysfs node.
-
-What:		/sys/class/extcon/.../state
-Date:		February 2012
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		The /sys/class/extcon/.../state shows and stores the cable
-		attach/detach information of the corresponding extcon object.
-		If the extcon object has an optional callback "show_state"
-		defined, the showing function is overridden with the optional
-		callback.
-
-		If the default callback for showing function is used, the
-		format is like this:
-		# cat state
-		USB_OTG=1
-		HDMI=0
-		TA=1
-		EAR_JACK=0
-		#
-		In this example, the extcon device has USB_OTG and TA
-		cables attached and HDMI and EAR_JACK cables detached.
-
-		In order to update the state of an extcon device, enter a hex
-		state number starting with 0x:
-		# echo 0xHEX > state
-
-		This updates the whole state of the extcon device.
-		Inputs of all the methods are required to meet the
-		mutually_exclusive conditions if they exist.
-
-		It is recommended to use this "global" state interface if
-		you need to set the value atomically. The later state
-		interface associated with each cable cannot update
-		multiple cable states of an extcon device simultaneously.
-
-What:		/sys/class/extcon/.../cable.x/name
-Date:		February 2012
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		The /sys/class/extcon/.../cable.x/name shows the name of cable
-		"x" (integer between 0 and 31) of an extcon device.
-
-What:		/sys/class/extcon/.../cable.x/state
-Date:		February 2012
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		The /sys/class/extcon/.../cable.x/state shows and stores the
-		state of cable "x" (integer between 0 and 31) of an extcon
-		device. The state value is either 0 (detached) or 1
-		(attached).
-
-What:		/sys/class/extcon/.../mutually_exclusive/...
-Date:		December 2011
-Contact:	MyungJoo Ham <myungjoo.ham@samsung.com>
-Description:
-		Shows the relations of mutually exclusiveness. For example,
-		if the mutually_exclusive array of extcon device is
-		{0x3, 0x5, 0xC, 0x0}, then the output is:
-		# ls mutually_exclusive/
-		0x3
-		0x5
-		0xc
-		#
-
-		Note that mutually_exclusive is a sub-directory of the extcon
-		device and the file names under the mutually_exclusive
-		directory show the mutually-exclusive sets, not the contents
-		of the files.

Documentation/ABI/testing/sysfs-class-iommu

@@ -1,17 +0,0 @@
-What:		/sys/class/iommu/<iommu>/devices/
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		IOMMU drivers are able to link devices managed by a
-		given IOMMU here to allow association of IOMMU to
-		device.
-
-What:		/sys/devices/.../iommu
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		IOMMU drivers are able to link the IOMMU for a
-		given device here to allow association of device to
-		IOMMU.

Documentation/ABI/testing/sysfs-class-iommu-amd-iommu

@@ -1,14 +0,0 @@
-What:		/sys/class/iommu/<iommu>/amd-iommu/cap
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		IOMMU capability header as documented in the AMD IOMMU
-		specification.  Format: %x
-
-What:		/sys/class/iommu/<iommu>/amd-iommu/features
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		Extended features of the IOMMU.  Format: %llx

Documentation/ABI/testing/sysfs-class-iommu-intel-iommu

@@ -1,32 +0,0 @@
-What:		/sys/class/iommu/<iommu>/intel-iommu/address
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		Physical address of the VT-d DRHD for this IOMMU.
-		Format: %llx.  This allows association of a sysfs
-		intel-iommu with a DMAR DRHD table entry.
-
-What:		/sys/class/iommu/<iommu>/intel-iommu/cap
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		The cached hardware capability register value
-		of this DRHD unit.  Format: %llx.
-
-What:		/sys/class/iommu/<iommu>/intel-iommu/ecap
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		The cached hardware extended capability register
-		value of this DRHD unit.  Format: %llx.
-
-What:		/sys/class/iommu/<iommu>/intel-iommu/version
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	Alex Williamson <alex.williamson@redhat.com>
-Description:
-		The architecture version as reported from the
-		VT-d VER_REG.  Format: %d:%d, major:minor

Documentation/ABI/testing/sysfs-class-led-driver-lm3533

@@ -1,65 +0,0 @@
-What:		/sys/class/leds/<led>/als_channel
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the ALS output channel to use as input in
-		ALS-current-control mode (1, 2), where
-
-		1 - out_current1
-		2 - out_current2
-
-What:		/sys/class/leds/<led>/als_en
-Date:		May 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Enable ALS-current-control mode (0, 1).
-
-What:		/sys/class/leds/<led>/falltime
-What:		/sys/class/leds/<led>/risetime
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the pattern generator fall and rise times (0..7), where
-
-		0 - 2048 us
-		1 - 262 ms
-		2 - 524 ms
-		3 - 1.049 s
-		4 - 2.097 s
-		5 - 4.194 s
-		6 - 8.389 s
-		7 - 16.78 s
-
-What:		/sys/class/leds/<led>/id
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Get the id of this led (0..3).
-
-What:		/sys/class/leds/<led>/linear
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the brightness-mapping mode (0, 1), where
-
-		0 - exponential mode
-		1 - linear mode
-
-What:		/sys/class/leds/<led>/pwm
-Date:		April 2012
-KernelVersion:	3.5
-Contact:	Johan Hovold <jhovold@gmail.com>
-Description:
-		Set the PWM-input control mask (5 bits), where
-
-		bit 5 - PWM-input enabled in Zone 4
-		bit 4 - PWM-input enabled in Zone 3
-		bit 3 - PWM-input enabled in Zone 2
-		bit 2 - PWM-input enabled in Zone 1
-		bit 1 - PWM-input enabled in Zone 0
-		bit 0 - PWM-input enabled

Documentation/ABI/testing/sysfs-class-leds-gt683r

@@ -1,16 +0,0 @@
-What:		/sys/class/leds/<led>/gt683r/mode
-Date:		Jun 2014
-KernelVersion:	3.17
-Contact:	Janne Kanniainen <janne.kanniainen@gmail.com>
-Description:
-		Set the mode of LEDs. You should notice that changing the mode
-		of one LED will update the mode of its two sibling devices as
-		well.
-
-		0 - normal
-		1 - audio
-		2 - breathing
-
-		Normal: LEDs are fully on when enabled
-		Audio:  LEDs brightness depends on sound level
-		Breathing: LEDs brightness varies at human breathing rate

Documentation/ABI/testing/sysfs-class-mei

@@ -1,16 +0,0 @@
-What:		/sys/class/mei/
-Date:		May 2014
-KernelVersion:	3.17
-Contact:	Tomas Winkler <tomas.winkler@intel.com>
-Description:
-		The mei/ class sub-directory belongs to mei device class
-
-
-What:		/sys/class/mei/meiN/
-Date:		May 2014
-KernelVersion:	3.17
-Contact:	Tomas Winkler <tomas.winkler@intel.com>
-Description:
-		The /sys/class/mei/meiN directory is created for
-		each probed mei device
-

Documentation/ABI/testing/sysfs-class-mic.txt

@@ -1,157 +0,0 @@
-What:		/sys/class/mic/
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		The mic class directory belongs to Intel MIC devices and
-		provides information per MIC device. An Intel MIC device is a
-		PCIe form factor add-in Coprocessor card based on the Intel Many
-		Integrated Core (MIC) architecture that runs a Linux OS.
-
-What:		/sys/class/mic/mic(x)
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		The directories /sys/class/mic/mic0, /sys/class/mic/mic1 etc.,
-		represent MIC devices (0,1,..etc). Each directory has
-		information specific to that MIC device.
-
-What:		/sys/class/mic/mic(x)/family
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		Provides information about the Coprocessor family for an Intel
-		MIC device. For example - "x100"
-
-What:		/sys/class/mic/mic(x)/stepping
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		Provides information about the silicon stepping for an Intel
-		MIC device. For example - "A0" or "B0"
-
-What:		/sys/class/mic/mic(x)/state
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		When read, this entry provides the current state of an Intel
-		MIC device in the context of the card OS. Possible values that
-		will be read are:
-		"offline" - The MIC device is ready to boot the card OS. On
-		reading this entry after an OSPM resume, a "boot" has to be
-		written to this entry if the card was previously shutdown
-		during OSPM suspend.
-		"online" - The MIC device has initiated booting a card OS.
-		"shutting_down" - The card OS is shutting down.
-		"reset_failed" - The MIC device has failed to reset.
-		"suspending" - The MIC device is currently being prepared for
-		suspend. On reading this entry, a "suspend" has to be written
-		to the state sysfs entry to ensure the card is shutdown during
-		OSPM suspend.
-		"suspended" - The MIC device has been suspended.
-
-		When written, this sysfs entry triggers different state change
-		operations depending upon the current state of the card OS.
-		Acceptable values are:
-		"boot" - Boot the card OS image specified by the combination
-			 of firmware, ramdisk, cmdline and bootmode
-			sysfs entries.
-		"reset" - Initiates device reset.
-		"shutdown" - Initiates card OS shutdown.
-		"suspend" - Initiates card OS shutdown and also marks the card
-		as suspended.
-
-What:		/sys/class/mic/mic(x)/shutdown_status
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		An Intel MIC device runs a Linux OS during its operation. This
-		OS can shutdown because of various reasons. When read, this
-		entry provides the status on why the card OS was shutdown.
-		Possible values are:
-		"nop" -  shutdown status is not applicable, when the card OS is
-			"online"
-		"crashed" - Shutdown because of a HW or SW crash.
-		"halted" - Shutdown because of a halt command.
-		"poweroff" - Shutdown because of a poweroff command.
-		"restart" - Shutdown because of a restart command.
-
-What:		/sys/class/mic/mic(x)/cmdline
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		An Intel MIC device runs a Linux OS during its operation. Before
-		booting this card OS, it is possible to pass kernel command line
-		options to configure various features in it, similar to
-		self-bootable machines. When read, this entry provides
-		information about the current kernel command line options set to
-		boot the card OS. This entry can be written to change the
-		existing kernel command line options. Typically, the user would
-		want to read the current command line options, append new ones
-		or modify existing ones and then write the whole kernel command
-		line back to this entry.
-
-What:		/sys/class/mic/mic(x)/firmware
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		When read, this sysfs entry provides the path name under
-		/lib/firmware/ where the firmware image to be booted on the
-		card can be found. The entry can be written to change the
-		firmware image location under /lib/firmware/.
-
-What:		/sys/class/mic/mic(x)/ramdisk
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		When read, this sysfs entry provides the path name under
-		/lib/firmware/ where the ramdisk image to be used during card
-		OS boot can be found. The entry can be written to change
-		the ramdisk image location under /lib/firmware/.
-
-What:		/sys/class/mic/mic(x)/bootmode
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		When read, this sysfs entry provides the current bootmode for
-		the card. This sysfs entry can be written with the following
-		valid strings:
-		a) linux - Boot a Linux image.
-		b) elf - Boot an elf image for flash updates.
-
-What:		/sys/class/mic/mic(x)/log_buf_addr
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		An Intel MIC device runs a Linux OS during its operation. For
-		debugging purpose and early kernel boot messages, the user can
-		access the card OS log buffer via debugfs. When read, this entry
-		provides the kernel virtual address of the buffer where the card
-		OS log buffer can be read. This entry is written by the host
-		configuration daemon to set the log buffer address. The correct
-		log buffer address to be written can be found in the System.map
-		file of the card OS.
-
-What:		/sys/class/mic/mic(x)/log_buf_len
-Date:		October 2013
-KernelVersion:	3.13
-Contact:	Sudeep Dutt <sudeep.dutt@intel.com>
-Description:
-		An Intel MIC device runs a Linux OS during its operation. For
-		debugging purpose and early kernel boot messages, the user can
-		access the card OS log buffer via debugfs. When read, this entry
-		provides the kernel virtual address where the card OS log buffer
-		length can be read. This entry is written by host configuration
-		daemon to set the log buffer length address. The correct log
-		buffer length address to be written can be found in the
-		System.map file of the card OS.

Documentation/ABI/testing/sysfs-class-mtd

@@ -14,7 +14,8 @@ Description:
 		The /sys/class/mtd/mtd{0,1,2,3,...} directories correspond
 		to each /dev/mtdX character device.  These may represent
 		physical/simulated flash devices, partitions on a flash
-		device, or concatenated flash devices.
+		device, or concatenated flash devices.  They exist regardless
+		of whether CONFIG_MTD_CHAR is actually enabled.
 
 What:		/sys/class/mtd/mtdXro/
 Date:		April 2009
@@ -22,7 +23,8 @@ KernelVersion:	2.6.29
 Contact:	linux-mtd@lists.infradead.org
 Description:
 		These directories provide the corresponding read-only device
-		nodes for /sys/class/mtd/mtdX/ .
+		nodes for /sys/class/mtd/mtdX/ .  They are only created
+		(for the benefit of udev) if CONFIG_MTD_CHAR is enabled.
 
 What:		/sys/class/mtd/mtdX/dev
 Date:		April 2009
@@ -104,7 +106,7 @@ Description:
 		One of the following ASCII strings, representing the device
 		type:
 
-		absent, ram, rom, nor, nand, mlc-nand, dataflash, ubi, unknown
+		absent, ram, rom, nor, nand, dataflash, ubi, unknown
 
 What:		/sys/class/mtd/mtdX/writesize
 Date:		April 2009
@@ -121,104 +123,3 @@ Description:
 		half page, or a quarter page).
 
 		In the case of ECC NOR, it is the ECC block size.
-
-What:		/sys/class/mtd/mtdX/ecc_strength
-Date:		April 2012
-KernelVersion:	3.4
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		Maximum number of bit errors that the device is capable of
-		correcting within each region covering an ECC step (see
-		ecc_step_size).  This will always be a non-negative integer.
-
-		In the case of devices lacking any ECC capability, it is 0.
-
-What:		/sys/class/mtd/mtdX/bitflip_threshold
-Date:		April 2012
-KernelVersion:	3.4
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		This allows the user to examine and adjust the criteria by which
-		mtd returns -EUCLEAN from mtd_read() and mtd_read_oob().  If the
-		maximum number of bit errors that were corrected on any single
-		region comprising an ecc step (as reported by the driver) equals
-		or exceeds this value, -EUCLEAN is returned.  Otherwise, absent
-		an error, 0 is returned.  Higher layers (e.g., UBI) use this
-		return code as an indication that an erase block may be
-		degrading and should be scrutinized as a candidate for being
-		marked as bad.
-
-		The initial value may be specified by the flash device driver.
-		If not, then the default value is ecc_strength.
-
-		The introduction of this feature brings a subtle change to the
-		meaning of the -EUCLEAN return code.  Previously, it was
-		interpreted to mean simply "one or more bit errors were
-		corrected".  Its new interpretation can be phrased as "a
-		dangerously high number of bit errors were corrected on one or
-		more regions comprising an ecc step".  The precise definition of
-		"dangerously high" can be adjusted by the user with
-		bitflip_threshold.  Users are discouraged from doing this,
-		however, unless they know what they are doing and have intimate
-		knowledge of the properties of their device.  Broadly speaking,
-		bitflip_threshold should be low enough to detect genuine erase
-		block degradation, but high enough to avoid the consequences of
-		a persistent return value of -EUCLEAN on devices where sticky
-		bitflips occur.  Note that if bitflip_threshold exceeds
-		ecc_strength, -EUCLEAN is never returned by the read operations.
-		Conversely, if bitflip_threshold is zero, -EUCLEAN is always
-		returned, absent a hard error.
-
-		This is generally applicable only to NAND flash devices with ECC
-		capability.  It is ignored on devices lacking ECC capability;
-		i.e., devices for which ecc_strength is zero.
-
-What:		/sys/class/mtd/mtdX/ecc_step_size
-Date:		May 2013
-KernelVersion:	3.10
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		The size of a single region covered by ECC, known as the ECC
-		step.  Devices may have several equally sized ECC steps within
-		each writesize region.
-
-		It will always be a non-negative integer.  In the case of
-		devices lacking any ECC capability, it is 0.
-
-What:		/sys/class/mtd/mtdX/ecc_failures
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		The number of failures reported by this device's ECC. Typically,
-		these failures are associated with failed read operations.
-
-		It will always be a non-negative integer.  In the case of
-		devices lacking any ECC capability, it is 0.
-
-What:		/sys/class/mtd/mtdX/corrected_bits
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		The number of bits that have been corrected by means of the
-		device's ECC.
-
-		It will always be a non-negative integer.  In the case of
-		devices lacking any ECC capability, it is 0.
-
-What:		/sys/class/mtd/mtdX/bad_blocks
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		The number of blocks marked as bad, if any, in this partition.
-
-What:		/sys/class/mtd/mtdX/bbt_blocks
-Date:		June 2014
-KernelVersion:	3.17
-Contact:	linux-mtd@lists.infradead.org
-Description:
-		The number of blocks that are marked as reserved, if any, in
-		this partition. These are typically used to store the in-flash
-		bad block table (BBT).

Documentation/ABI/testing/sysfs-class-net

@@ -1,218 +0,0 @@
-What:		/sys/class/net/<iface>/name_assign_type
-Date:		July 2014
-KernelVersion:	3.17
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the name assignment type. Possible values are:
-		1: enumerated by the kernel, possibly in an unpredictable way
-		2: predictably named by the kernel
-		3: named by userspace
-		4: renamed
-
-What:		/sys/class/net/<iface>/addr_assign_type
-Date:		July 2010
-KernelVersion:	3.2
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the address assignment type. Possible values are:
-		0: permanent address
-		1: randomly generated
-		2: stolen from another device
-		3: set using dev_set_mac_address
-
-What:		/sys/class/net/<iface>/addr_len
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the hardware address size in bytes.
-		Values vary based on the lower-level protocol used by the
-		interface (Ethernet, FDDI, ATM, IEEE 802.15.4...). See
-		include/uapi/linux/if_*.h for actual values.
-
-What:		/sys/class/net/<iface>/address
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Hardware address currently assigned to this interface.
-		Format is a string, e.g: 00:11:22:33:44:55 for an Ethernet MAC
-		address.
-
-What:		/sys/class/net/<iface>/broadcast
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Hardware broadcast address for this interface. Format is a
-		string, e.g: ff:ff:ff:ff:ff:ff for an Ethernet broadcast MAC
-		address.
-
-What:		/sys/class/net/<iface>/carrier
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the current physical link state of the interface.
-		Posssible values are:
-		0: physical link is down
-		1: physical link is up
-
-		Note: some special devices, e.g: bonding and team drivers will
-		allow this attribute to be written to force a link state for
-		operating correctly and designating another fallback interface.
-
-What:		/sys/class/net/<iface>/dev_id
-Date:		April 2008
-KernelVersion:	2.6.26
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the device unique identifier. Format is an hexadecimal
-		value. This is used to disambiguate interfaces which might be
-		stacked (e.g: VLAN interfaces) but still have the same MAC
-		address as their parent device.
-
-What:		/sys/class/net/<iface>/dormant
-Date:		March 2006
-KernelVersion:	2.6.17
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates whether the interface is in dormant state. Possible
-		values are:
-		0: interface is not dormant
-		1: interface is dormant
-
-		This attribute can be used by supplicant software to signal that
-		the device is not usable unless some supplicant-based
-		authentication is performed (e.g: 802.1x). 'link_mode' attribute
-		will also reflect the dormant state.
-
-What:		/sys/clas/net/<iface>/duplex
-Date:		October 2009
-KernelVersion:	2.6.33
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface latest or current duplex value. Possible
-		values are:
-		half: half duplex
-		full: full duplex
-
-		Note: This attribute is only valid for interfaces that implement
-		the ethtool get_settings method (mostly Ethernet).
-
-What:		/sys/class/net/<iface>/flags
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface flags as a bitmask in hexadecimal. See
-		include/uapi/linux/if.h for a list of all possible values and
-		the flags semantics.
-
-What:		/sys/class/net/<iface>/ifalias
-Date:		September 2008
-KernelVersion:	2.6.28
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates/stores an interface alias name as a string. This can
-		be used for system management purposes.
-
-What:		/sys/class/net/<iface>/ifindex
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the system-wide interface unique index identifier as a
-		decimal number. This attribute is used for mapping an interface
-		identifier to an interface name. It is used throughout the
-		networking stack for specifying the interface specific
-		requests/events.
-
-What:		/sys/class/net/<iface>/iflink
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the system-wide interface unique index identifier a
-		the interface is linked to. Format is decimal. This attribute is
-		used to resolve interfaces chaining, linking and stacking.
-		Physical interfaces have the same 'ifindex' and 'iflink' values.
-
-What:		/sys/class/net/<iface>/link_mode
-Date:		March 2006
-KernelVersion:	2.6.17
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface link mode, as a decimal number. This
-		attribute should be used in conjunction with 'dormant' attribute
-		to determine the interface usability. Possible values:
-		0: default link mode
-		1: dormant link mode
-
-What:		/sys/class/net/<iface>/mtu
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface currently configured MTU value, in
-		bytes, and in decimal format. Specific values depends on the
-		lower-level interface protocol used. Ethernet devices will show
-		a 'mtu' attribute value of 1500 unless changed.
-
-What:		/sys/class/net/<iface>/netdev_group
-Date:		January 2011
-KernelVersion:	2.6.39
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface network device group, as a decimal
-		integer. Default value is 0 which corresponds to the initial
-		network devices group. The group can be changed to affect
-		routing decisions (see: net/ipv4/fib_rules and
-		net/ipv6/fib6_rules.c).
-
-What:		/sys/class/net/<iface>/operstate
-Date:		March 2006
-KernelVersion:	2.6.17
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface RFC2863 operational state as a string.
-		Possible values are:
-		"unknown", "notpresent", "down", "lowerlayerdown", "testing",
-		"dormant", "up".
-
-What:		/sys/class/net/<iface>/phys_port_id
-Date:		July 2013
-KernelVersion:	3.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface unique physical port identifier within
-		the NIC, as a string.
-
-What:		/sys/class/net/<iface>/speed
-Date:		October 2009
-KernelVersion:	2.6.33
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface latest or current speed value. Value is
-		an integer representing the link speed in Mbits/sec.
-
-		Note: this attribute is only valid for interfaces that implement
-		the ethtool get_settings method (mostly Ethernet ).
-
-What:		/sys/class/net/<iface>/tx_queue_len
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface transmit queue len in number of packets,
-		as an integer value. Value depend on the type of interface,
-		Ethernet network adapters have a default value of 1000 unless
-		configured otherwise
-
-What:		/sys/class/net/<iface>/type
-Date:		April 2005
-KernelVersion:	2.6.12
-Contact:	netdev@vger.kernel.org
-Description:
-		Indicates the interface protocol type as a decimal value. See
-		include/uapi/linux/if_arp.h for all possible values.

Documentation/ABI/testing/sysfs-class-net-batman-adv

@@ -1,15 +1,14 @@
 
-What:           /sys/class/net/<iface>/batman-adv/iface_status
-Date:           May 2010
-Contact:        Marek Lindner <mareklindner@neomailbox.ch>
-Description:
-                Indicates the status of <iface> as it is seen by batman.
-
 What:           /sys/class/net/<iface>/batman-adv/mesh_iface
 Date:           May 2010
-Contact:        Marek Lindner <mareklindner@neomailbox.ch>
+Contact:        Marek Lindner <lindner_marek@yahoo.de>
 Description:
                 The /sys/class/net/<iface>/batman-adv/mesh_iface file
                 displays the batman mesh interface this <iface>
                 currently is associated with.
 
+What:           /sys/class/net/<iface>/batman-adv/iface_status
+Date:           May 2010
+Contact:        Marek Lindner <lindner_marek@yahoo.de>
+Description:
+                Indicates the status of <iface> as it is seen by batman.