Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history 
yaml
---
r: 155620
b: refs/heads/master
c: 4859484
h: refs/heads/master
v: v3
  • Loading branch information
Jiri Slaby authored and Jiri Kosina committed Jun 22, 2009
1 parent 7ac9866 commit 4c1a6a9
Show file tree
Hide file tree
Showing 5,988 changed files with 350,136 additions and 539,226 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: 0dc3d523e8bc4718e0be2e4a742367d6e4be77cd
refs/heads/master: 4859484b0957ddc7fe3e0fa349d98b0f1c7876bd
1 change: 0 additions & 1 deletion trunk/.gitignore
View file
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,6 @@
*.gz
*.lzma
*.patch
*.gcno

#
# Top-level generic files
Expand Down
4 changes: 0 additions & 4 deletions trunk/CREDITS
View file
Original file line number Diff line number Diff line change
Expand Up @@ -1253,10 +1253,6 @@ S: 8124 Constitution Apt. 7
S: Sterling Heights, Michigan 48313
S: USA

N: Wolfgang Grandegger
E: wg@grandegger.com
D: Controller Area Network (device drivers)

N: William Greathouse
E: wgreathouse@smva.com
E: wgreathouse@myfavoritei.com
Expand Down
7 changes: 0 additions & 7 deletions trunk/Documentation/ABI/testing/sysfs-bus-pci
View file
Original file line number Diff line number Diff line change
Expand Up @@ -122,10 +122,3 @@ Description:
This symbolic link appears when a device is a Virtual Function.
The symbolic link points to the PCI device sysfs entry of the
Physical Function this device associates with.

What: /sys/bus/pci/slots/.../module
Date: June 2009
Contact: linux-pci@vger.kernel.org
Description:
This symbolic link points to the PCI hotplug controller driver
module that manages the hotplug slot.
125 changes: 0 additions & 125 deletions trunk/Documentation/ABI/testing/sysfs-class-mtd
View file

This file was deleted.

10 changes: 0 additions & 10 deletions trunk/Documentation/ABI/testing/sysfs-fs-ext4
View file
Original file line number Diff line number Diff line change
Expand Up @@ -79,13 +79,3 @@ Description:
This file is read-only and shows the number of
kilobytes of data that have been written to this
filesystem since it was mounted.

What: /sys/fs/ext4/<disk>/inode_goal
Date: June 2008
Contact: "Theodore Ts'o" <tytso@mit.edu>
Description:
Tuning parameter which (if non-zero) controls the goal
inode used by the inode allocator in p0reference to
all other allocation hueristics. This is intended for
debugging use only, and should be 0 on production
systems.
73 changes: 0 additions & 73 deletions trunk/Documentation/ABI/testing/sysfs-pps
View file

This file was deleted.

7 changes: 0 additions & 7 deletions trunk/Documentation/Changes
View file
Original file line number Diff line number Diff line change
Expand Up @@ -72,13 +72,6 @@ assembling the 16-bit boot code, removing the need for as86 to compile
your kernel. This change does, however, mean that you need a recent
release of binutils.

Perl
----

You will need perl 5 and the following modules: Getopt::Long, Getopt::Std,
File::Basename, and File::Find to build the kernel.


System utilities
================

Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/DocBook/debugobjects.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -106,7 +106,7 @@
number of errors are printk'ed including a full stack trace.
</para>
<para>
The statistics are available via /sys/kernel/debug/debug_objects/stats.
The statistics are available via debugfs/debug_objects/stats.
They provide information about the number of warnings and the
number of successful fixups along with information about the
usage of the internal tracking objects and the state of the
Expand Down
3 changes: 3 additions & 0 deletions trunk/Documentation/DocBook/mac80211.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -145,6 +145,7 @@ usage should require reading the full document.
interface in STA mode at first!
</para>
!Finclude/net/mac80211.h ieee80211_if_init_conf
!Finclude/net/mac80211.h ieee80211_if_conf
</chapter>

<chapter id="rx-tx">
Expand Down Expand Up @@ -184,6 +185,8 @@ usage should require reading the full document.
!Finclude/net/mac80211.h ieee80211_ctstoself_get
!Finclude/net/mac80211.h ieee80211_ctstoself_duration
!Finclude/net/mac80211.h ieee80211_generic_frame_duration
!Finclude/net/mac80211.h ieee80211_get_hdrlen_from_skb
!Finclude/net/mac80211.h ieee80211_hdrlen
!Finclude/net/mac80211.h ieee80211_wake_queue
!Finclude/net/mac80211.h ieee80211_stop_queue
!Finclude/net/mac80211.h ieee80211_wake_queues
Expand Down
25 changes: 0 additions & 25 deletions trunk/Documentation/PCI/pcieaer-howto.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -61,10 +61,6 @@ be initiated although firmwares have no _OSC support. To enable the
walkaround, pls. add aerdriver.forceload=y to kernel boot parameter line
when booting kernel. Note that forceload=n by default.

nosourceid, another parameter of type bool, can be used when broken
hardware (mostly chipsets) has root ports that cannot obtain the reporting
source ID. nosourceid=n by default.

2.3 AER error output
When a PCI-E AER error is captured, an error message will be outputed to
console. If it's a correctable error, it is outputed as a warning.
Expand Down Expand Up @@ -250,24 +246,3 @@ with the PCI Express AER Root driver?
A: It could call the helper functions to enable AER in devices and
cleanup uncorrectable status register. Pls. refer to section 3.3.


4. Software error injection

Debugging PCIE AER error recovery code is quite difficult because it
is hard to trigger real hardware errors. Software based error
injection can be used to fake various kinds of PCIE errors.

First you should enable PCIE AER software error injection in kernel
configuration, that is, following item should be in your .config.

CONFIG_PCIEAER_INJECT=y or CONFIG_PCIEAER_INJECT=m

After reboot with new kernel or insert the module, a device file named
/dev/aer_inject should be created.

Then, you need a user space tool named aer-inject, which can be gotten
from:
http://www.kernel.org/pub/linux/utils/pci/aer-inject/

More information about aer-inject can be found in the document comes
with its source code.
2 changes: 1 addition & 1 deletion trunk/Documentation/SubmitChecklist
View file
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ kernel patches.
CONFIG_PREEMPT.

14: If the patch affects IO/Disk, etc: has been tested with and without
CONFIG_LBDAF.
CONFIG_LBD.

15: All codepaths have been exercised with all lockdep features enabled.

Expand Down
3 changes: 1 addition & 2 deletions trunk/Documentation/accounting/getdelays.c
View file
Original file line number Diff line number Diff line change
Expand Up @@ -246,8 +246,7 @@ void print_ioacct(struct taskstats *t)

int main(int argc, char *argv[])
{
int c, rc, rep_len, aggr_len, len2;
int cmd_type = TASKSTATS_CMD_ATTR_UNSPEC;
int c, rc, rep_len, aggr_len, len2, cmd_type;
__u16 id;
__u32 mypid;

Expand Down
4 changes: 2 additions & 2 deletions trunk/Documentation/atomic_ops.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -229,10 +229,10 @@ kernel. It is the use of atomic counters to implement reference
counting, and it works such that once the counter falls to zero it can
be guaranteed that no other entity can be accessing the object:

static void obj_list_add(struct obj *obj, struct list_head *head)
static void obj_list_add(struct obj *obj)
{
obj->active = 1;
list_add(&obj->list, head);
list_add(&obj->list);
}

static void obj_list_del(struct obj *obj)
Expand Down
4 changes: 2 additions & 2 deletions trunk/Documentation/block/data-integrity.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ encouraged them to allow separation of the data and integrity metadata
scatter-gather lists.

The controller will interleave the buffers on write and split them on
read. This means that Linux can DMA the data buffers to and from
read. This means that the Linux can DMA the data buffers to and from
host memory without changes to the page cache.

Also, the 16-bit CRC checksum mandated by both the SCSI and SATA specs
Expand All @@ -66,7 +66,7 @@ software RAID5).

The IP checksum is weaker than the CRC in terms of detecting bit
errors. However, the strength is really in the separation of the data
buffers and the integrity metadata. These two distinct buffers must
buffers and the integrity metadata. These two distinct buffers much
match up for an I/O to complete.

The separation of the data and integrity metadata buffers as well as
Expand Down
2 changes: 1 addition & 1 deletion trunk/Documentation/cdrom/packet-writing.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -117,7 +117,7 @@ Using the pktcdvd debugfs interface

To read pktcdvd device infos in human readable form, do:

# cat /sys/kernel/debug/pktcdvd/pktcdvd[0-7]/info
# cat /debug/pktcdvd/pktcdvd[0-7]/info

For a description of the debugfs interface look into the file:

Expand Down
Loading

0 comments on commit 4c1a6a9

Please sign in to comment.