Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history 
yaml
---
r: 303155
b: refs/heads/master
c: 4711244
h: refs/heads/master
i:
  303153: cfbac66
  303151: baf2693
v: v3
  • Loading branch information
Benoit Cousson committed Mar 7, 2012
1 parent 4ce1d12 commit 06acadd
Show file tree
Hide file tree
Showing 12,572 changed files with 465,805 additions and 700,408 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
2 changes: 1 addition & 1 deletion [refs]
View file
Original file line number Diff line number Diff line change
@@ -1,2 +1,2 @@
---
refs/heads/master: 8dca6010d44cc722a94dc6da96560f9083dac782
refs/heads/master: 4711244c764da806fc9d14793c0664f3709ef17d
6 changes: 2 additions & 4 deletions trunk/Documentation/00-INDEX
View file
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@ Please try and keep the descriptions small enough to fit on one line.

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.
Expand Down Expand Up @@ -104,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/
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/obsolete/sysfs-class-rfkill
View file
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/removed/devfs
View file
Original file line number Diff line number Diff line change
@@ -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
Expand Down
9 changes: 0 additions & 9 deletions trunk/Documentation/ABI/removed/ip_queue
View file

This file was deleted.

26 changes: 13 additions & 13 deletions trunk/Documentation/ABI/stable/sysfs-driver-usb-usbtmc
View file
Original file line number Diff line number Diff line change
@@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/stable/sysfs-module
View file
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ Description:
The name of the module that is in the kernel. This
module name will show up either if the module is built
directly into the kernel, or if it is loaded as a
dynamic module.
dyanmic module.

/sys/module/MODULENAME/parameters
This directory contains individual files that are each
Expand Down
16 changes: 0 additions & 16 deletions trunk/Documentation/ABI/testing/debugfs-olpc
View file

This file was deleted.

25 changes: 0 additions & 25 deletions trunk/Documentation/ABI/testing/sysfs-block-dm
View file

This file was deleted.

18 changes: 0 additions & 18 deletions trunk/Documentation/ABI/testing/sysfs-block-rssd
View file

This file was deleted.

14 changes: 0 additions & 14 deletions trunk/Documentation/ABI/testing/sysfs-bus-event_source-devices-format
View file

This file was deleted.

19 changes: 0 additions & 19 deletions trunk/Documentation/ABI/testing/sysfs-bus-hsi
View file

This file was deleted.

75 changes: 0 additions & 75 deletions trunk/Documentation/ABI/testing/sysfs-bus-rpmsg
View file

This file was deleted.

11 changes: 0 additions & 11 deletions trunk/Documentation/ABI/testing/sysfs-bus-usb
View file
Original file line number Diff line number Diff line change
Expand Up @@ -182,14 +182,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 decriptor bits and platform-specific data
such as ACPI. This file will read either "removable" or
"fixed" if the information is available, and "unknown"
otherwise.
8 changes: 0 additions & 8 deletions trunk/Documentation/ABI/testing/sysfs-cfq-target-latency
View file

This file was deleted.

2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/testing/sysfs-class
View file
Original file line number Diff line number Diff line change
@@ -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
Expand Down
16 changes: 0 additions & 16 deletions trunk/Documentation/ABI/testing/sysfs-class-net-mesh
View file
Original file line number Diff line number Diff line change
Expand Up @@ -14,15 +14,6 @@ Description:
mesh will be sent using multiple interfaces at the
same time (if available).

What: /sys/class/net/<mesh_iface>/mesh/bridge_loop_avoidance
Date: November 2011
Contact: Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
Description:
Indicates whether the bridge loop avoidance feature
is enabled. This feature detects and avoids loops
between the mesh and devices bridged with the soft
interface <mesh_iface>.

What: /sys/class/net/<mesh_iface>/mesh/fragmentation
Date: October 2010
Contact: Andreas Langer <an.langer@gmx.de>
Expand Down Expand Up @@ -74,13 +65,6 @@ Description:
Defines the penalty which will be applied to an
originator message's tq-field on every hop.

What: /sys/class/net/<mesh_iface>/mesh/routing_algo
Date: Dec 2011
Contact: Marek Lindner <lindner_marek@yahoo.de>
Description:
Defines the routing procotol this mesh instance
uses to find the optimal paths through the mesh.

What: /sys/class/net/<mesh_iface>/mesh/vis_mode
Date: May 2010
Contact: Marek Lindner <lindner_marek@yahoo.de>
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/ABI/testing/sysfs-devices
View file
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
What: /sys/devices
Date: February 2006
Contact: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Contact: Greg Kroah-Hartman <gregkh@suse.de>
Description:
The /sys/devices tree contains a snapshot of the
internal state of the kernel device tree. Devices will
Expand Down
18 changes: 0 additions & 18 deletions trunk/Documentation/ABI/testing/sysfs-devices-power
View file
Original file line number Diff line number Diff line change
Expand Up @@ -165,21 +165,3 @@ Description:

Not all drivers support this attribute. If it isn't supported,
attempts to read or write it will yield I/O errors.

What: /sys/devices/.../power/pm_qos_latency_us
Date: March 2012
Contact: Rafael J. Wysocki <rjw@sisk.pl>
Description:
The /sys/devices/.../power/pm_qos_resume_latency_us attribute
contains the PM QoS resume latency limit for the given device,
which is the maximum allowed time it can take to resume the
device, after it has been suspended at run time, from a resume
request to the moment the device will be ready to process I/O,
in microseconds. If it is equal to 0, however, this means that
the PM QoS resume latency may be arbitrary.

Not all drivers support this attribute. If it isn't supported,
it is not present.

This attribute has no effect on system-wide suspend/resume and
hibernation.
Loading

0 comments on commit 06acadd

Please sign in to comment.