Skip to content

Commit

Permalink
---
Browse files Browse the repository at this point in the history 
yaml
---
r: 222082
b: refs/heads/master
c: 1c66b36
h: refs/heads/master
v: v3
  • Loading branch information
Tao Ma authored and Joel Becker committed Nov 13, 2010
1 parent 8010c29 commit 2dfe362
Show file tree
Hide file tree
Showing 1,769 changed files with 61,552 additions and 56,942 deletions.
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: 0143832cc96d0bf78486297aad5c8fb2c2ead02a
refs/heads/master: 1c66b360fe26204e2aa14e45086b4a6b8890b1a2
22 changes: 0 additions & 22 deletions trunk/Documentation/ABI/obsolete/proc-pid-oom_adj
View file

This file was deleted.

13 changes: 1 addition & 12 deletions trunk/Documentation/DocBook/kgdb.tmpl
View file
Original file line number Diff line number Diff line change
Expand Up @@ -710,18 +710,7 @@ Task Addr Pid Parent [*] cpu State Thread Command
<listitem><para>A simple shell</para></listitem>
<listitem><para>The kdb core command set</para></listitem>
<listitem><para>A registration API to register additional kdb shell commands.</para>
<itemizedlist>
<listitem><para>A good example of a self-contained kdb module
is the "ftdump" command for dumping the ftrace buffer. See:
kernel/trace/trace_kdb.c</para></listitem>
<listitem><para>For an example of how to dynamically register
a new kdb command you can build the kdb_hello.ko kernel module
from samples/kdb/kdb_hello.c. To build this example you can
set CONFIG_SAMPLES=y and CONFIG_SAMPLE_KDB=m in your kernel
config. Later run "modprobe kdb_hello" and the next time you
enter the kdb shell, you can run the "hello"
command.</para></listitem>
</itemizedlist></listitem>
<para>A good example of a self-contained kdb module is the "ftdump" command for dumping the ftrace buffer. See: kernel/trace/trace_kdb.c</para></listitem>
<listitem><para>The implementation for kdb_printf() which
emits messages directly to I/O drivers, bypassing the kernel
log.</para></listitem>
Expand Down
8 changes: 4 additions & 4 deletions trunk/Documentation/block/switching-sched.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,7 @@ you can do so by typing:
As of the Linux 2.6.10 kernel, it is now possible to change the
IO scheduler for a given block device on the fly (thus making it possible,
for instance, to set the CFQ scheduler for the system default, but
set a specific device to use the deadline or noop schedulers - which
set a specific device to use the anticipatory or noop schedulers - which
can improve that device's throughput).

To set a specific scheduler, simply do this:
Expand All @@ -31,7 +31,7 @@ a "cat /sys/block/DEV/queue/scheduler" - the list of valid names
will be displayed, with the currently selected scheduler in brackets:

# cat /sys/block/hda/queue/scheduler
noop deadline [cfq]
# echo deadline > /sys/block/hda/queue/scheduler
noop anticipatory deadline [cfq]
# echo anticipatory > /sys/block/hda/queue/scheduler
# cat /sys/block/hda/queue/scheduler
noop [deadline] cfq
noop [anticipatory] deadline cfq
50 changes: 11 additions & 39 deletions trunk/Documentation/coccinelle.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -24,9 +24,6 @@ of many distributions, e.g. :
You can get the latest version released from the Coccinelle homepage at
http://coccinelle.lip6.fr/

Information and tips about Coccinelle are also provided on the wiki
pages at http://cocci.ekstranet.diku.dk/wiki/doku.php

Once you have it, run the following command:

./configure
Expand All @@ -44,22 +41,20 @@ A Coccinelle-specific target is defined in the top level
Makefile. This target is named 'coccicheck' and calls the 'coccicheck'
front-end in the 'scripts' directory.

Four modes are defined: patch, report, context, and org. The mode to
Four modes are defined: report, patch, context, and org. The mode to
use is specified by setting the MODE variable with 'MODE=<mode>'.

'patch' proposes a fix, when possible.

'report' generates a list in the following format:
file:line:column-column: message

'patch' proposes a fix, when possible.

'context' highlights lines of interest and their context in a
diff-like style.Lines of interest are indicated with '-'.

'org' generates a report in the Org mode format of Emacs.

Note that not all semantic patches implement all modes. For easy use
of Coccinelle, the default mode is "chain" which tries the previous
modes in the order above until one succeeds.
Note that not all semantic patches implement all modes.

To make a report for every semantic patch, run the following command:

Expand All @@ -73,9 +68,9 @@ To produce patches, run:


The coccicheck target applies every semantic patch available in the
sub-directories of 'scripts/coccinelle' to the entire Linux kernel.
subdirectories of 'scripts/coccinelle' to the entire Linux kernel.

For each semantic patch, a commit message is proposed. It gives a
For each semantic patch, a changelog message is proposed. It gives a
description of the problem being checked by the semantic patch, and
includes a reference to Coccinelle.

Expand All @@ -98,35 +93,12 @@ or
make coccicheck COCCI=<my_SP.cocci> MODE=report


Using Coccinelle on (modified) files
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

To apply Coccinelle on a file basis, instead of a directory basis, the
following command may be used:

make C=1 CHECK="scripts/coccicheck"

To check only newly edited code, use the value 2 for the C flag, i.e.

make C=2 CHECK="scripts/coccicheck"

This runs every semantic patch in scripts/coccinelle by default. The
COCCI variable may additionally be used to only apply a single
semantic patch as shown in the previous section.

The "chain" mode is the default. You can select another one with the
MODE variable explained above.

In this mode, there is no information about semantic patches
displayed, and no commit message proposed.


Proposing new semantic patches
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

New semantic patches can be proposed and submitted by kernel
developers. For sake of clarity, they should be organized in the
sub-directories of 'scripts/coccinelle/'.
subdirectories of 'scripts/coccinelle/'.


Detailed description of the 'report' mode
Expand All @@ -139,7 +111,7 @@ Example:

Running

make coccicheck MODE=report COCCI=scripts/coccinelle/api/err_cast.cocci
make coccicheck MODE=report COCCI=scripts/coccinelle/err_cast.cocci

will execute the following part of the SmPL script.

Expand Down Expand Up @@ -177,7 +149,7 @@ identified.
Example:

Running
make coccicheck MODE=patch COCCI=scripts/coccinelle/api/err_cast.cocci
make coccicheck MODE=patch COCCI=scripts/coccinelle/err_cast.cocci

will execute the following part of the SmPL script.

Expand Down Expand Up @@ -221,7 +193,7 @@ NOTE: The diff-like output generated is NOT an applicable patch. The
Example:

Running
make coccicheck MODE=context COCCI=scripts/coccinelle/api/err_cast.cocci
make coccicheck MODE=context COCCI=scripts/coccinelle/err_cast.cocci

will execute the following part of the SmPL script.

Expand Down Expand Up @@ -256,7 +228,7 @@ diff -u -p /home/user/linux/crypto/ctr.c /tmp/nothing
Example:

Running
make coccicheck MODE=org COCCI=scripts/coccinelle/api/err_cast.cocci
make coccicheck MODE=org COCCI=scripts/coccinelle/err_cast.cocci

will execute the following part of the SmPL script.

Expand Down
2 changes: 2 additions & 0 deletions trunk/Documentation/filesystems/Locking
View file
Original file line number Diff line number Diff line change
Expand Up @@ -322,13 +322,15 @@ fl_release_private: yes yes
prototypes:
int (*fl_compare_owner)(struct file_lock *, struct file_lock *);
void (*fl_notify)(struct file_lock *); /* unblock callback */
void (*fl_copy_lock)(struct file_lock *, struct file_lock *);
void (*fl_release_private)(struct file_lock *);
void (*fl_break)(struct file_lock *); /* break_lease callback */

locking rules:
BKL may block
fl_compare_owner: yes no
fl_notify: yes no
fl_copy_lock: yes no
fl_release_private: yes yes
fl_break: yes no

Expand Down
11 changes: 11 additions & 0 deletions trunk/Documentation/filesystems/xfs-delayed-logging-design.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -794,6 +794,17 @@ designed.

Roadmap:

2.6.37 Remove experimental tag from mount option
=> should be roughly 6 months after initial merge
=> enough time to:
=> gain confidence and fix problems reported by early
adopters (a.k.a. guinea pigs)
=> address worst performance regressions and undesired
behaviours
=> start tuning/optimising code for parallelism
=> start tuning/optimising algorithms consuming
excessive CPU time

2.6.39 Switch default mount option to use delayed logging
=> should be roughly 12 months after initial merge
=> enough time to shake out remaining problems before next round of
Expand Down
6 changes: 1 addition & 5 deletions trunk/Documentation/i2c/busses/i2c-i801
View file
Original file line number Diff line number Diff line change
Expand Up @@ -15,14 +15,10 @@ Supported adapters:
* Intel 82801I (ICH9)
* Intel EP80579 (Tolapai)
* Intel 82801JI (ICH10)
* Intel 5/3400 Series (PCH)
* Intel 3400/5 Series (PCH)
* Intel Cougar Point (PCH)
* Intel Patsburg (PCH)
Datasheets: Publicly available at the Intel website

On Intel Patsburg and later chipsets, both the normal host SMBus controller
and the additional 'Integrated Device Function' controllers are supported.

Authors:
Mark Studebaker <mdsxyz123@yahoo.com>
Jean Delvare <khali@linux-fr.org>
Expand Down
3 changes: 1 addition & 2 deletions trunk/Documentation/kbuild/kconfig-language.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -322,8 +322,7 @@ mainmenu:
"mainmenu" <prompt>

This sets the config program's title bar if the config program chooses
to use it. It should be placed at the top of the configuration, before any
other statement.
to use it.


Kconfig hints
Expand Down
7 changes: 0 additions & 7 deletions trunk/Documentation/kbuild/makefiles.txt
View file
Original file line number Diff line number Diff line change
Expand Up @@ -776,13 +776,6 @@ This will delete the directory debian, including all subdirectories.
Kbuild will assume the directories to be in the same relative path as the
Makefile if no absolute path is specified (path does not start with '/').

To exclude certain files from make clean, use the $(no-clean-files) variable.
This is only a special case used in the top level Kbuild file:

Example:
#Kbuild
no-clean-files := $(bounds-file) $(offsets-file)

Usually kbuild descends down in subdirectories due to "obj-* := dir/",
but in the architecture makefiles where the kbuild infrastructure
is not sufficient this sometimes needs to be explicit.
Expand Down
Loading

0 comments on commit 2dfe362

Please sign in to comment.