Skip to content

cloud-kernel
cloud-kernel

openanolis / cloud-kernel
1 年多 前同步成功

通知 161
Star 36
Fork 7
cloud-kernel
cloud-kernel
提交 c00046c2 编写于 作者: L Linus Torvalds
浏览文件
操作

Merge git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial 

* git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial: (74 commits)
  fix do_sys_open() prototype
  sysfs: trivial: fix sysfs_create_file kerneldoc spelling mistake
  Documentation: Fix typo in SubmitChecklist.
  Typo: depricated -> deprecated
  Add missing profile=kvm option to Documentation/kernel-parameters.txt
  fix typo about TBI in e1000 comment
  proc.txt: Add /proc/stat field
  small documentation fixes
  Fix compiler warning in smount example program from sharedsubtree.txt
  docs/sysfs: add missing word to sysfs attribute explanation
  documentation/ext3: grammar fixes
  Documentation/java.txt: typo and grammar fixes
  Documentation/filesystems/vfs.txt: typo fix
  include/asm-*/system.h: remove unused set_rmb(), set_wmb() macros
  trivial copy_data_pages() tidy up
  Fix typo in arch/x86/kernel/tsc_32.c
  file link fix for Pegasus USB net driver help
  remove unused return within void return function
  Typo fixes retrun -> return
  x86 hpet.h: remove broken links
  ...
上级 9abbf7d0 8e8a1407
展开全部 隐藏空白更改
内联 并排
Showing with 879 addition and 943 deletion
CREDITS
浏览文件 @ c00046c2
......@@ -959,7 +959,7 @@ S: 2037 Walnut #6
S: Boulder, Colorado 80302
S: USA
N: Heiko Eissfeldt
N: Heiko Eißfeldt
E: heiko@colossus.escape.de heiko@unifix.de
D: verify_area stuff, generic SCSI fixes
D: SCSI Programming HOWTO
......@@ -1988,8 +1988,8 @@ N: Volker Lendecke
E: vl@kki.org
D: Kernel smbfs (to mount WfW, NT and OS/2 network drives.)
D: NCP filesystem support (to mount NetWare volumes)
S: Von Ossietzky Str. 12
S: 37085 Goettingen
S: Von-Ossietzky-Str. 12
S: 37085 Göttingen
S: Germany
N: Kevin Lentin
......@@ -2431,11 +2431,11 @@ S: 12725 SW Millikan Way, Suite 400
S: Beaverton, Oregon 97005
S: USA
N: Eberhard Moenkeberg
N: Eberhard Mönkeberg
E: emoenke@gwdg.de
D: CDROM driver "sbpcd" (Matsushita/Panasonic/Soundblaster)
S: Ruhstrathoehe 2 b.
S: D-37085 Goettingen
S: Ruhstrathöhe 2 b.
S: D-37085 Göttingen
S: Germany
N: Thomas Molina
......
Documentation/DocBook/Makefile
浏览文件 @ c00046c2
......@@ -165,7 +165,7 @@ quiet_cmd_db2man = MAN $@
@touch $@
###
# Rules to generate postscripts and PNG imgages from .fig format files
# Rules to generate postscripts and PNG images from .fig format files
quiet_cmd_fig2eps = FIG2EPS $@
cmd_fig2eps = fig2dev -Leps $< $@
......
Documentation/DocBook/mtdnand.tmpl
浏览文件 @ c00046c2
......@@ -282,7 +282,7 @@ int __init board_init (void)
goto out;
}
/* map physical adress */
/* map physical address */
baseaddr = (unsigned long)ioremap(CHIP_PHYSICAL_ADDRESS, 1024);
if(!baseaddr){
printk("Ioremap to access NAND chip failed\n");
......@@ -306,7 +306,7 @@ int __init board_init (void)
this->dev_ready = board_dev_ready;
this->eccmode = NAND_ECC_SOFT;
/* Scan to find existance of the device */
/* Scan to find existence of the device */
if (nand_scan (board_mtd, 1)) {
err = -ENXIO;
goto out_ior;
......@@ -340,7 +340,7 @@ static void __exit board_cleanup (void)
/* Release resources, unregister device */
nand_release (board_mtd);
/* unmap physical adress */
/* unmap physical address */
iounmap((void *)baseaddr);
/* Free the MTD device structure */
......
Documentation/SubmitChecklist
浏览文件 @ c00046c2
......@@ -67,7 +67,7 @@ kernel patches.
20: Check that it all passes `make headers_check'.
21: Has been checked with injection of at least slab and page-allocation
fauilures. See Documentation/fault-injection/.
failures. See Documentation/fault-injection/.
If the new code is substantial, addition of subsystem-specific fault
injection might be appropriate.
......
Documentation/SubmittingDrivers
浏览文件 @ c00046c2
......@@ -36,8 +36,7 @@ Linux 2.4:
If the code area has a general maintainer then please submit it to
the maintainer listed in MAINTAINERS in the kernel file. If the
maintainer does not respond or you cannot find the appropriate
maintainer then please contact Marcelo Tosatti
<marcelo.tosatti@cyclades.com>.
maintainer then please contact Willy Tarreau <w@1wt.eu>.
Linux 2.6:
The same rules apply as 2.4 except that you should follow linux-kernel
......
Documentation/arm/Samsung-S3C24XX/DMA.txt
浏览文件 @ c00046c2
......@@ -5,7 +5,7 @@ Introduction
------------
The kernel provides an interface to manage DMA transfers
using the DMA channels in the cpu, so that the central
using the DMA channels in the CPU, so that the central
duty of managing channel mappings, and programming the
channel generators is in one place.
......@@ -17,24 +17,24 @@ DMA Channel Ordering
channels to all sources, which means that some devices
have a restricted number of channels that can be used.
To allow flexibilty for each cpu type and board, the
dma code can be given an dma ordering structure which
To allow flexibility for each CPU type and board, the
DMA code can be given a DMA ordering structure which
allows the order of channel search to be specified, as
well as allowing the prohibition of certain claims.
struct s3c24xx_dma_order has a list of channels, and
each channel within has a slot for a list of dma
channel numbers. The slots are searched in order, for
the presence of a dma channel number with DMA_CH_VALID
orred in.
each channel within has a slot for a list of DMA
channel numbers. The slots are searched in order for
the presence of a DMA channel number with DMA_CH_VALID
or-ed in.
If the order has the flag DMA_CH_NEVER set, then after
checking the channel list, the system will return no
found channel, thus denying the request.
A board support file can call s3c24xx_dma_order_set()
to register an complete ordering set. The routine will
copy the data, so the original can be discared with
to register a complete ordering set. The routine will
copy the data, so the original can be discarded with
__initdata.
......
Documentation/cdrom/cdrom-standard.tex
浏览文件 @ c00046c2
......@@ -1009,7 +1009,7 @@ taken over the torch in maintaining \cdromc\ and integrating much
\cdrom-related code in the 2.1-kernel. Thanks to Scott Snyder and
Gerd Knorr, who were the first to implement this interface for SCSI
and IDE-CD drivers and added many ideas for extension of the data
structures relative to kernel~2.0. Further thanks to Heiko Eissfeldt,
structures relative to kernel~2.0. Further thanks to Heiko Ei{\sz}feldt,
Thomas Quinot, Jon Tombs, Ken Pizzini, Eberhard M\"onkeberg and Andrew
Kroll, the \linux\ \cdrom\ device driver developers who were kind
enough to give suggestions and criticisms during the writing. Finally
......
Documentation/devices.txt
浏览文件 @ c00046c2
......@@ -2188,7 +2188,7 @@ Your cooperation is appreciated.
136-143 char Unix98 PTY slaves
0 = /dev/pts/0 First Unix98 pseudo-TTY
1 = /dev/pts/1 Second Unix98 pesudo-TTY
1 = /dev/pts/1 Second Unix98 pseudo-TTY
...
These device nodes are automatically generated with
......
Documentation/driver-model/devres.txt
浏览文件 @ c00046c2
......@@ -32,7 +32,7 @@ braindamaged document, if it's finally working, well, it's working.
For one reason or another, low level drivers don't receive as much
attention or testing as core code, and bugs on driver detach or
initilaization failure doesn't happen often enough to be noticeable.
initialization failure don't happen often enough to be noticeable.
Init failure path is worse because it's much less travelled while
needs to handle multiple entry points.
......@@ -160,7 +160,7 @@ resources on failure. For example,
devres_release_group(dev, NULL);
return err_code;
As resource acquision failure usually means probe failure, constructs
As resource acquisition failure usually means probe failure, constructs
like above are usually useful in midlayer driver (e.g. libata core
layer) where interface function shouldn't have side effect on failure.
For LLDs, just returning error code suffices in most cases.
......
Documentation/fb/deferred_io.txt
浏览文件 @ c00046c2
......@@ -3,7 +3,7 @@ Deferred IO
Deferred IO is a way to delay and repurpose IO. It uses host memory as a
buffer and the MMU pagefault as a pretrigger for when to perform the device
IO. The following example may be a useful explaination of how one such setup
IO. The following example may be a useful explanation of how one such setup
works:
- userspace app like Xfbdev mmaps framebuffer
......@@ -28,7 +28,7 @@ a relatively more expensive operation.
For some types of nonvolatile high latency displays, the desired image is
the final image rather than the intermediate stages which is why it's okay
to not update for each write that is occuring.
to not update for each write that is occurring.
It may be the case that this is useful in other scenarios as well. Paul Mundt
has mentioned a case where it is beneficial to use the page count to decide
......
Documentation/filesystems/9p.txt
浏览文件 @ c00046c2
......@@ -54,7 +54,7 @@ OPTIONS
aname=name aname specifies the file tree to access when the server is
offering several exported file systems.
cache=mode specifies a cacheing policy. By default, no caches are used.
cache=mode specifies a caching policy. By default, no caches are used.
loose = no attempts are made at consistency,
intended for exclusive, read-only mounts
......
Documentation/filesystems/Locking
浏览文件 @ c00046c2
......@@ -224,7 +224,7 @@ against the page the filesystem should redirty the page with
redirty_page_for_writepage(), then unlock the page and return zero.
This may also be done to avoid internal deadlocks, but rarely.
If the filesytem is called for sync then it must wait on any
If the filesystem is called for sync then it must wait on any
in-progress I/O and then start new I/O.
The filesystem should unlock the page synchronously, before returning to the
......
Documentation/filesystems/ext3.txt
浏览文件 @ c00046c2
......@@ -130,12 +130,12 @@ Device layer.
Journaling Block Device layer
-----------------------------
The Journaling Block Device layer (JBD) isn't ext3 specific. It was design to
add journaling capabilities on a block device. The ext3 filesystem code will
inform the JBD of modifications it is performing (called a transaction). The
journal supports the transactions start and stop, and in case of crash, the
journal can replayed the transactions to put the partition back in a
consistent state fast.
The Journaling Block Device layer (JBD) isn't ext3 specific. It was designed
to add journaling capabilities to a block device. The ext3 filesystem code
will inform the JBD of modifications it is performing (called a transaction).
The journal supports the transactions start and stop, and in case of a crash,
the journal can replay the transactions to quickly put the partition back into
a consistent state.
Handles represent a single atomic update to a filesystem. JBD can handle an
external journal on a block device.
......@@ -164,7 +164,7 @@ written to the journal first, and then to its final location.
In the event of a crash, the journal can be replayed, bringing both data and
metadata into a consistent state. This mode is the slowest except when data
needs to be read from and written to disk at the same time where it
outperforms all others modes.
outperforms all other modes.
Compatibility
-------------
......
Documentation/filesystems/files.txt
浏览文件 @ c00046c2
......@@ -76,13 +76,13 @@ the fdtable structure -
5. Handling of the file structures is special. Since the look-up
of the fd (fget()/fget_light()) are lock-free, it is possible
that look-up may race with the last put() operation on the
file structure. This is avoided using the rcuref APIs
file structure. This is avoided using atomic_inc_not_zero()
on ->f_count :
rcu_read_lock();
file = fcheck_files(files, fd);
if (file) {
if (rcuref_inc_lf(&file->f_count))
if (atomic_inc_not_zero(&file->f_count))
*fput_needed = 1;
else
/* Didn't get the reference, someone's freed */
......@@ -92,7 +92,7 @@ the fdtable structure -
....
return file;
rcuref_inc_lf() detects if refcounts is already zero or
atomic_inc_not_zero() detects if refcounts is already zero or
goes to zero during increment. If it does, we fail
fget()/fget_light().
......
Documentation/filesystems/proc.txt
浏览文件 @ c00046c2
......@@ -813,9 +813,9 @@ Various pieces of information about kernel activity are available in the
since the system first booted. For a quick look, simply cat the file:
> cat /proc/stat
cpu 2255 34 2290 22625563 6290 127 456
cpu0 1132 34 1441 11311718 3675 127 438
cpu1 1123 0 849 11313845 2614 0 18
cpu 2255 34 2290 22625563 6290 127 456 0
cpu0 1132 34 1441 11311718 3675 127 438 0
cpu1 1123 0 849 11313845 2614 0 18 0
intr 114930548 113199788 3 0 5 263 0 4 [... lots more numbers ...]
ctxt 1990473
btime 1062191376
......@@ -835,6 +835,7 @@ second). The meanings of the columns are as follows, from left to right:
- iowait: waiting for I/O to complete
- irq: servicing interrupts
- softirq: servicing softirqs
- steal: involuntary wait
The "intr" line gives counts of interrupts serviced since boot time, for each
of the possible system interrupts. The first column is the total of all
......
Documentation/filesystems/sysfs.txt
浏览文件 @ c00046c2
......@@ -51,7 +51,7 @@ for the attributes, providing a means to read and write kernel
attributes.
Attributes should be ASCII text files, preferably with only one value
per file. It is noted that it may not be efficient to contain only
per file. It is noted that it may not be efficient to contain only one
value per file, so it is socially acceptable to express an array of
values of the same type.
......
Documentation/filesystems/vfs.txt
浏览文件 @ c00046c2
......@@ -706,7 +706,7 @@ struct address_space_operations {
wants to make it a free page. If ->releasepage succeeds, the
page will be removed from the address_space and become free.
The second case if when a request has been made to invalidate
The second case is when a request has been made to invalidate
some or all pages in an address_space. This can happen
through the fadvice(POSIX_FADV_DONTNEED) system call or by the
filesystem explicitly requesting it as nfs and 9fs do (when
......
Documentation/i2c/i2c-protocol
浏览文件 @ c00046c2
......@@ -68,7 +68,7 @@ We have found some I2C devices that needs the following modifications:
Flags I2C_M_IGNORE_NAK
Normally message is interrupted immediately if there is [NA] from the
client. Setting this flag treats any [NA] as [A], and all of
client. Setting this flag treats any [NA] as [A], and all of
message is sent.
These messages may still fail to SCL lo->hi timeout.
......
Documentation/ia64/err_inject.txt
浏览文件 @ c00046c2
......@@ -21,10 +21,10 @@ software test suits to do stressful testing on IPF.
Below is a sample application as part of the whole tool. The sample
can be used as a working test tool. Or it can be expanded to include
more features. It also can be a integrated into a libary or other user
more features. It also can be a integrated into a library or other user
application to have more thorough test.
The sample application takes err.conf as error configuation input. Gcc
The sample application takes err.conf as error configuration input. GCC
compiles the code. After you install err_inject driver, you can run
this sample application to inject errors.
......@@ -809,7 +809,7 @@ int err_inj()
}
/* Create semaphore: If one_lock, one semaphore for all processors.
Otherwise, one sempaphore for each processor. */
Otherwise, one semaphore for each processor. */
if (one_lock) {
if (create_sem(0)) {
printf("Can not create semaphore...exit\n");
......
Documentation/input/atarikbd.txt
浏览文件 @ c00046c2
......@@ -170,7 +170,7 @@ major controller faults (ROM checksum and RAM test) and such things as stuck
keys. Any keys down at power-up are presumed to be stuck, and their BREAK
(sic) code is returned (which without the preceding MAKE code is a flag for a
keyboard error). If the controller self-test completes without error, the code
0xF0 is returned. (This code will be used to indicate the version/rlease of
0xF0 is returned. (This code will be used to indicate the version/release of
the ikbd controller. The first release of the ikbd is version 0xF0, should
there be a second release it will be 0xF1, and so on.)
The ikbd defaults to a mouse position reporting with threshold of 1 unit in
......@@ -413,7 +413,7 @@ INTERROGATION MODE.
%nnnnmmmm ; where m is JOYSTICK1 state
; and n is JOYSTICK0 state
Sets the ikbd to do nothing but monitor the serial command lne, maintain the
Sets the ikbd to do nothing but monitor the serial command line, maintain the
time-of-day clock, and monitor the joystick. The rate sets the interval
between joystick samples.
N.B. The user should not set the rate higher than the serial communications
......@@ -446,10 +446,10 @@ The sample interval should be as constant as possible.
; until vertical cursor key is generated before RY
; has elapsed
VX ; length (in tenths of seconds) of joystick closure
; until horizontal cursor keystokes are generated
; until horizontal cursor keystrokes are generated
; after RX has elapsed
VY ; length (in tenths of seconds) of joystick closure
; until vertical cursor keystokes are generated
; until vertical cursor keystrokes are generated
; after RY has elapsed
In this mode, joystick 0 is scanned in a way that simulates cursor keystrokes.
......
Documentation/input/ff.txt
浏览文件 @ c00046c2
Force feedback for Linux.
By Johann Deneux <deneux@ifrance.com> on 2001/04/22.
By Johann Deneux <johann.deneux@gmail.com> on 2001/04/22.
Updated by Anssi Hannula <anssi.hannula@gmail.com> on 2006/04/09.
You may redistribute this file. Please remember to include shape.fig and
interactive.fig as well.
......
Documentation/input/iforce-protocol.txt
浏览文件 @ c00046c2
......@@ -4,10 +4,10 @@ specify force effects to I-Force 2.0 devices. None of this information comes
from Immerse. That's why you should not trust what is written in this
document. This document is intended to help understanding the protocol.
This is not a reference. Comments and corrections are welcome. To contact me,
send an email to: deneux@ifrance.com
send an email to: johann.deneux@gmail.com
** WARNING **
I may not be held responsible for any dammage or harm caused if you try to
I shall not be held responsible for any damage or harm caused if you try to
send data to your I-Force device based on what you read in this document.
** Preliminary Notes:
......@@ -151,13 +151,13 @@ OP= ff
Query command. Length varies according to the query type.
The general format of this packet is:
ff 01 QUERY [INDEX] CHECKSUM
reponses are of the same form:
responses are of the same form:
FF LEN QUERY VALUE_QUERIED CHECKSUM2
where LEN = 1 + length(VALUE_QUERIED)
**** Query ram size ****
QUERY = 42 ('B'uffer size)
The device should reply with the same packet plus two additionnal bytes
The device should reply with the same packet plus two additional bytes
containing the size of the memory:
ff 03 42 03 e8 CS would mean that the device has 1000 bytes of ram available.
......@@ -234,19 +234,23 @@ is the amount of memory apparently needed for every set of parameters:
** Appendix: How to study the protocol ? **
1. Generate effects using the force editor provided with the DirectX SDK, or use Immersion Studio (freely available at their web site in the developer section: www.immersion.com)
2. Start a soft spying RS232 or USB (depending on where you connected your joystick/wheel). I used ComPortSpy from fCoder (alpha version!)
1. Generate effects using the force editor provided with the DirectX SDK, or
use Immersion Studio (freely available at their web site in the developer section:
www.immersion.com)
2. Start a soft spying RS232 or USB (depending on where you connected your
joystick/wheel). I used ComPortSpy from fCoder (alpha version!)
3. Play the effect, and watch what happens on the spy screen.
A few words about ComPortSpy:
At first glance, this soft seems, hum, well... buggy. In fact, data appear with a few seconds latency. Personnaly, I restart it every time I play an effect.
At first glance, this software seems, hum, well... buggy. In fact, data appear with a
few seconds latency. Personally, I restart it every time I play an effect.
Remember it's free (as in free beer) and alpha!
** URLS **
Check www.immerse.com for Immersion Studio, and www.fcoder.com for ComPortSpy.
** Author of this document **
Johann Deneux <deneux@ifrance.com>
Johann Deneux <johann.deneux@gmail.com>
Home page at http://www.esil.univ-mrs.fr/~jdeneux/projects/ff/
Additions by Vojtech Pavlik.
......
Documentation/input/input-programming.txt
浏览文件 @ c00046c2
......@@ -79,7 +79,7 @@ In the _init function, which is called either upon module load or when
booting the kernel, it grabs the required resources (it should also check
for the presence of the device).
Then it allocates a new input device structure with input_aloocate_device()
Then it allocates a new input device structure with input_allocate_device()
and sets up input bitfields. This way the device driver tells the other
parts of the input systems what it is - what events can be generated or
accepted by this input device. Our example device can only generate EV_KEY
......
Documentation/isdn/CREDITS
浏览文件 @ c00046c2
......@@ -40,7 +40,7 @@ Andreas Kool (akool@Kool.f.EUnet.de)
Pedro Roque Marques (roque@di.fc.ul.pt)
For lot of new ideas and the pcbit driver.
Eberhard Moenkeberg (emoenke@gwdg.de)
Eberhard Mönkeberg (emoenke@gwdg.de)
For testing and help to get into kernel.
Thomas Neumann (tn@ruhr.de)
......
Documentation/isdn/README.concap
浏览文件 @ c00046c2
......@@ -111,7 +111,7 @@ struct concap_proto_ops{
struct concap_proto * (*proto_new) (void);
/* delete encapsulation protocol instance and free all its resources.
cprot may no loger be referenced after calling this */
cprot may no longer be referenced after calling this */
void (*proto_del)(struct concap_proto *cprot);
/* initialize the protocol's data. To be called at interface startup
......
Documentation/java.txt
浏览文件 @ c00046c2
......@@ -37,7 +37,7 @@ other program after you have done the following:
or the following, if you want to be more selective:
':Applet:M::<!--applet::/usr/bin/appletviewer:'
Of cause you have to fix the path names. Given path/file names in this
Of course you have to fix the path names. The path/file names given in this
document match the Debian 2.1 system. (i.e. jdk installed in /usr,
custom wrappers from this document in /usr/local)
......
Documentation/kernel-docs.txt
浏览文件 @ c00046c2
......@@ -76,9 +76,9 @@
* Title: "Conceptual Architecture of the Linux Kernel"
Author: Ivan T. Bowman.
URL: http://plg.uwaterloo.ca/~itbowman/papers/CS746G-a1.html
Keywords: conceptual software arquitecture, extracted design,
Keywords: conceptual software architecture, extracted design,
reverse engineering, system structure.
Description: Conceptual software arquitecture of the Linux kernel,
Description: Conceptual software architecture of the Linux kernel,
automatically extracted from the source code. Very detailed. Good
figures. Gives good overall kernel understanding.
......
Documentation/kernel-parameters.txt
浏览文件 @ c00046c2
......@@ -222,9 +222,6 @@ and is between 256 and 4096 characters. It is defined in the file
Warning: Many of these options can produce a lot of
output and make your system unusable. Be very careful.
acpi_fake_ecdt [HW,ACPI] Workaround failure due to BIOS lacking ECDT
acpi_pm_good [X86-32,X86-64]
Override the pmtimer bug detection: force the kernel
to assume that this machine's pmtimer latches its value
......@@ -297,9 +294,6 @@ and is between 256 and 4096 characters. It is defined in the file
apm= [APM] Advanced Power Management
See header of arch/i386/kernel/apm.c.
applicom= [HW]
Format: <mem>,<irq>
arcrimi= [HW,NET] ARCnet - "RIM I" (entirely mem-mapped) cards
Format: <io>,<irq>,<nodeID>
......@@ -345,12 +339,6 @@ and is between 256 and 4096 characters. It is defined in the file
Format: <io>,<irq>,<mode>
See header of drivers/net/hamradio/baycom_ser_hdx.c.
blkmtd_device= [HW,MTD]
blkmtd_erasesz=
blkmtd_ro=
blkmtd_bs=
blkmtd_count=
boot_delay= Milliseconds to delay each printk during boot.
Values larger than 10 seconds (10000) are changed to
no delay (0).
......@@ -515,8 +503,6 @@ and is between 256 and 4096 characters. It is defined in the file
cs89x0_media= [HW,NET]
Format: { rj45 | aui | bnc }
cyclades= [HW,SERIAL] Cyclades multi-serial port adapter.
dasd= [HW,NET]
See header of drivers/s390/block/dasd_devmap.c.
......@@ -574,10 +560,6 @@ and is between 256 and 4096 characters. It is defined in the file
See drivers/char/README.epca and
Documentation/digiepca.txt.
dmascc= [HW,AX25,SERIAL] AX.25 Z80SCC driver with DMA
support available.
Format: <io_dev0>[,<io_dev1>[,..<io_dev32>]]
dmasound= [HW,OSS] Sound subsystem buffers
dscc4.setup= [NET]
......@@ -608,17 +590,10 @@ and is between 256 and 4096 characters. It is defined in the file
0: polling mode
non-0: interrupt mode (default)
eda= [HW,PS2]
edb= [HW,PS2]
edd= [EDD]
Format: {"of[f]" | "sk[ipmbr]"}
See comment in arch/i386/boot/edd.S
eicon= [HW,ISDN]
Format: <id>,<membase>,<irq>
eisa_irq_edge= [PARISC,HW]
See header of drivers/parisc/eisa.c.
......@@ -894,9 +869,6 @@ and is between 256 and 4096 characters. It is defined in the file
lapic_timer_c2_ok [X86-32,x86-64,APIC] trust the local apic timer in
C2 power state.
lasi= [HW,SCSI] PARISC LASI driver for the 53c700 chip
Format: addr:<io>,irq:<irq>
libata.noacpi [LIBATA] Disables use of ACPI in libata suspend/resume
when set.
Format: <int>
......@@ -1144,9 +1116,6 @@ and is between 256 and 4096 characters. It is defined in the file
noapic [SMP,APIC] Tells the kernel to not make use of any
IOAPICs that may be present in the system.
noasync [HW,M68K] Disables async and sync negotiation for
all devices.
nobats [PPC] Do not use BATs for mapping kernel lowmem
on "Classic" PPC cores.
......@@ -1458,6 +1427,7 @@ and is between 256 and 4096 characters. It is defined in the file
Param: <number> - step/bucket size as a power of 2 for
statistical time based profiling.
Param: "sleep" - profile D-state sleeping (millisecs)
Param: "kvm" - profile VM exits.
processor.max_cstate= [HW,ACPI]
Limit processor to maximum C-state
......@@ -1584,9 +1554,6 @@ and is between 256 and 4096 characters. It is defined in the file
sa1100ir [NET]
See drivers/net/irda/sa1100_ir.c.
sb= [HW,OSS]
Format: <io>,<irq>,<dma>,<dma2>
sbni= [NET] Granch SBNI12 leased line adapter
sc1200wdt= [HW,WDT] SC1200 WDT (watchdog) driver
......@@ -1630,8 +1597,6 @@ and is between 256 and 4096 characters. It is defined in the file
serialnumber [BUGS=X86-32]
sg_def_reserved_size= [SCSI]
shapers= [NET]
Maximal number of shapers.
......@@ -2022,10 +1987,6 @@ and is between 256 and 4096 characters. It is defined in the file
norandmaps Don't use address space randomization
Equivalent to echo 0 > /proc/sys/kernel/randomize_va_space
unwind_debug=N N > 0 will enable dwarf2 unwinder debugging
This is useful to get more information why
you got a "dwarf2 unwinder stuck"
______________________________________________________________________
TODO:
......
Documentation/m68k/kernel-options.txt
浏览文件 @ c00046c2
......@@ -890,10 +890,7 @@ Syntax: nosync:0
5.5.2) noasync
--------------
Syntax: noasync:0
Disables async and sync negotiation for all devices. Any value
after the colon is acceptable (and has the same effect).
[OBSOLETE, REMOVED]
5.5.3) nodisconnect
-------------------
......
Documentation/mips/AU1xxx_IDE.README
浏览文件 @ c00046c2
......@@ -59,7 +59,7 @@ Four configs variables are introduced:
CONFIG_BLK_DEV_IDE_AU1XXX_PIO_DBDMA - enable the PIO+DBDMA mode
CONFIG_BLK_DEV_IDE_AU1XXX_MDMA2_DBDMA - enable the MWDMA mode
CONFIG_BLK_DEV_IDE_AU1XXX_BURSTABLE_ON - set Burstable FIFO in DBDMA
controler
controller
CONFIG_BLK_DEV_IDE_AU1XXX_SEQTS_PER_RQ - maximum transfer size
per descriptor
......
Documentation/mutex-design.txt
浏览文件 @ c00046c2
......@@ -133,4 +133,6 @@ the APIs of 'struct mutex' have been streamlined:
int mutex_trylock(struct mutex *lock);
void mutex_unlock(struct mutex *lock);
int mutex_is_locked(struct mutex *lock);
void mutex_lock_nested(struct mutex *lock, unsigned int subclass);
int mutex_lock_interruptible_nested(struct mutex *lock,
unsigned int subclass);
Documentation/networking/bcm43xx.txt
浏览文件 @ c00046c2
......@@ -37,7 +37,7 @@ all, distributions. There is, however, additional software that is
required. The firmware used by the chip is the intellectual property
of Broadcom and they have not given the bcm43xx team redistribution
rights to this firmware. Since we cannot legally redistribute
the firwmare we cannot include it with the driver. Furthermore, it
the firmware we cannot include it with the driver. Furthermore, it
cannot be placed in the downloadable archives of any distributing
organization; therefore, the user is responsible for obtaining the
firmware and placing it in the appropriate location so that the driver
......
Documentation/networking/ip-sysctl.txt
浏览文件 @ c00046c2
......@@ -293,7 +293,7 @@ tcp_no_metrics_save - BOOLEAN
when the connection closes, so that connections established in the
near future can use these to set initial conditions. Usually, this
increases overall performance, but may sometimes cause performance
degredation. If set, TCP will not cache metrics on closing
degradation. If set, TCP will not cache metrics on closing
connections.
tcp_orphan_retries - INTEGER
......
Documentation/networking/rxrpc.txt
浏览文件 @ c00046c2
......@@ -689,7 +689,7 @@ such as the AFS filesystem. This permits such a utility to:
buffers manipulated directly.
To use the RxRPC facility, a kernel utility must still open an AF_RXRPC socket,
bind an addess as appropriate and listen if it's to be a server socket, but
bind an address as appropriate and listen if it's to be a server socket, but
then it passes this to the kernel interface functions.
The kernel interface functions are as follows:
......
Documentation/networking/udplite.txt
浏览文件 @ c00046c2
......@@ -12,7 +12,7 @@
For in-depth information, you can consult:
o The UDP-Lite Homepage: http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/
Fom here you can also download some example application source code.
From here you can also download some example application source code.
o The UDP-Lite HOWTO on
http://www.erg.abdn.ac.uk/users/gerrit/udp-lite/files/UDP-Lite-HOWTO.txt
......@@ -223,7 +223,7 @@
While it is important that such cases are dealt with correctly, they
are (annoyingly) rare: UDP-Lite is designed for optimising multimedia
performance over wireless (or generally noisy) links and thus smaller
coverage lenghts are likely to be expected.
coverage lengths are likely to be expected.
V) UDP-LITE RUNTIME STATISTICS AND THEIR MEANING
......@@ -259,7 +259,7 @@
VI) IPTABLES
There is packet match support for UDP-Lite as well as support for the LOG target.
If you copy and paste the following line into /etc/protcols,
If you copy and paste the following line into /etc/protocols,
udplite 136 UDP-Lite # UDP-Lite [RFC 3828]
......
Documentation/power/swsusp-and-swap-files.txt
浏览文件 @ c00046c2
......@@ -39,7 +39,7 @@ resume=<swap_file_partition> resume_offset=<swap_file_offset>
where <swap_file_partition> is the partition on which the swap file is located
and <swap_file_offset> is the offset of the swap header determined by the
application in 2) (of course, this step may be carried out automatically
by the same application that determies the swap file's header offset using the
by the same application that determines the swap file's header offset using the
FIBMAP ioctl)
OR
......
Documentation/powerpc/eeh-pci-error-recovery.txt
浏览文件 @ c00046c2
......@@ -36,8 +36,8 @@ Causes of EEH Errors
EEH was originally designed to guard against hardware failure, such
as PCI cards dying from heat, humidity, dust, vibration and bad
electrical connections. The vast majority of EEH errors seen in
"real life" are due to eithr poorly seated PCI cards, or,
unfortunately quite commonly, due device driver bugs, device firmware
"real life" are due to either poorly seated PCI cards, or,
unfortunately quite commonly, due to device driver bugs, device firmware
bugs, and sometimes PCI card hardware bugs.
The most common software bug, is one that causes the device to
......
Documentation/powerpc/mpc52xx-device-tree-bindings.txt
浏览文件 @ c00046c2
......@@ -17,12 +17,12 @@ passed by the boot loader to the kernel at boot time. The device tree
describes what devices are present on the board and how they are
connected. The device tree can either be passed as a binary blob (as
described in Documentation/powerpc/booting-without-of.txt), or passed
by Open Firmare (IEEE 1275) compatible firmware using an OF compatible
by Open Firmware (IEEE 1275) compatible firmware using an OF compatible
client interface API.
This document specifies the requirements on the device-tree for mpc5200
based boards. These requirements are above and beyond the details
specified in either the OpenFirmware spec or booting-without-of.txt
specified in either the Open Firmware spec or booting-without-of.txt
All new mpc5200-based boards are expected to match this document. In
cases where this document is not sufficient to support a new board port,
......@@ -73,8 +73,8 @@ match on the compatible list; the 'most compatible' driver should be
selected.
The split between the MPC5200 and the MPC5200B leaves a bit of a
connundrum. How should the compatible property be set up to provide
maximum compatability information; but still acurately describe the
conundrum. How should the compatible property be set up to provide
maximum compatibility information; but still accurately describe the
chip? For the MPC5200; the answer is easy. Most of the SoC devices
originally appeared on the MPC5200. Since they didn't exist anywhere
else; the 5200 compatible properties will contain only one item;
......@@ -84,7 +84,7 @@ The 5200B is almost the same as the 5200, but not quite. It fixes
silicon bugs and it adds a small number of enhancements. Most of the
devices either provide exactly the same interface as on the 5200. A few
devices have extra functions but still have a backwards compatible mode.
To express this infomation as completely as possible, 5200B device trees
To express this information as completely as possible, 5200B device trees
should have two items in the compatible list;
"mpc5200b-<device>\0mpc5200-<device>". It is *strongly* recommended
that 5200B device trees follow this convention (instead of only listing
......@@ -199,7 +199,7 @@ ethernet@<addr> network mpc5200-fec MPC5200 ethernet device
ata@<addr> ata mpc5200-ata IDE ATA interface
i2c@<addr> i2c mpc5200-i2c I2C controller
usb@<addr> usb-ohci-be mpc5200-ohci,ohci-be USB controller
xlb@<addr> xlb mpc5200-xlb XLB arbritrator
xlb@<addr> xlb mpc5200-xlb XLB arbitrator
Important child node properties
name type description
......
Documentation/scsi/aic79xx.txt
浏览文件 @ c00046c2
......@@ -120,7 +120,7 @@ The following information is available in this file:
list size to avoid SCSI malloc pool fragmentation.
- Cleanup channel display in our /proc output.
- Workaround duplicate device entries in the mid-layer
devlice list during add-single-device.
device list during add-single-device.
1.3.6 (March 28th, 2003)
- Correct a double free in the Domain Validation code.
......
Documentation/scsi/aic7xxx.txt
浏览文件 @ c00046c2
......@@ -159,7 +159,7 @@ The following information is available in this file:
- Add support for 2.5.X's scsi_report_device_reset().
6.2.34 (May 5th, 2003)
- Fix locking regression instroduced in 6.2.29 that
- Fix locking regression introduced in 6.2.29 that
could cause a lock order reversal between the io_request_lock
and our per-softc lock. This was only possible on RH9,
SuSE, and kernel.org 2.4.X kernels.
......@@ -264,7 +264,7 @@ The following information is available in this file:
Option: tag_info:{{value[,value...]}[,{value[,value...]}...]}
Definition: Set the per-target tagged queue depth on a
per controller basis. Both controllers and targets
may be ommitted indicating that they should retain
may be omitted indicating that they should retain
the default tag depth.
Examples: tag_info:{{16,32,32,64,8,8,,32,32,32,32,32,32,32,32,32}
On Controller 0
......@@ -290,7 +290,7 @@ The following information is available in this file:
-----------------------------------------------------------------
Option: dv: {value[,value...]}
Definition: Set Domain Validation Policy on a per-controller basis.
Controllers may be ommitted indicating that
Controllers may be omitted indicating that
they should retain the default read streaming setting.
Example: dv:{-1,0,,1,1,0}
On Controller 0 leave DV at its default setting.
......
Documentation/scsi/arcmsr_spec.txt
浏览文件 @ c00046c2
......@@ -3,7 +3,7 @@
*******************************************************************************
** Usage of IOP331 adapter
** (All In/Out is in IOP331's view)
** 1. Message 0 --> InitThread message and retrun code
** 1. Message 0 --> InitThread message and return code
** 2. Doorbell is used for RS-232 emulation
** inDoorBell : bit0 -- data in ready
** (DRIVER DATA WRITE OK)
......
Documentation/scsi/ibmmca.txt
浏览文件 @ c00046c2
......@@ -21,7 +21,7 @@
versions older than 4.0 do not work with kernels 2.4.0 or later! If you
try to compile your kernel with the wrong driver source, the
compilation is aborted and you get a corresponding error message. This is
no bug in the driver. It prevents you from using the wrong sourcecode
no bug in the driver; it prevents you from using the wrong source code
with the wrong kernel version.
Authors of this Driver
......@@ -58,7 +58,7 @@
5 Users' Manual
5.1 Commandline Parameters
5.2 Troubleshooting
5.3 Bugreports
5.3 Bug reports
5.4 Support WWW-page
6 References
7 Credits to
......@@ -71,13 +71,13 @@
1 Abstract
----------
This README-file describes the IBM SCSI-subsystem low level driver for
Linux. The descriptions which were formerly kept in the source-code have
been taken out to this file to easify the codes' readability. The driver
This README-file describes the IBM SCSI-subsystem low level driver for
Linux. The descriptions which were formerly kept in the source code have
been taken out of this file to simplify the codes readability. The driver
description has been updated, as most of the former description was already
quite outdated. The history of the driver development is also kept inside
here. Multiple historical developments have been summarized to shorten the
textsize a bit. At the end of this file you can find a small manual for
quite outdated. The history of the driver development is also kept inside
here. Multiple historical developments have been summarized to shorten the
text size a bit. At the end of this file you can find a small manual for
this driver and hints to get it running on your machine.
2 Driver Description
......@@ -186,7 +186,7 @@
between 0 and 7). The IBM SCSI-2 F/W adapter offers this on up to two
busses and provides support for 30 logical devices at the same time, where
in wide-addressing mode you can have 16 puns with 32 luns on each device.
This section dexribes you the handling of devices on non-F/W adapters.
This section describes the handling of devices on non-F/W adapters.
Just imagine, that you can have 16 * 32 = 512 devices on a F/W adapter
which means a lot of possible devices for such a small machine.
......@@ -209,10 +209,10 @@
--------------------------------------------------------
One consequence of information hiding is that the real (pun,lun)
numbers are also hidden. The two possibilities to get around this problem
is to offer fake pun/lun combinations to the operating system or to
are to offer fake pun/lun combinations to the operating system or to
delete the whole mapping of the adapter and to reassign the ldns, using
the immediate assign command of the SCSI-subsystem for probing through
all possible pun/lun combinations. a ldn is a "logical device number"
all possible pun/lun combinations. An ldn is a "logical device number"
which is used by IBM SCSI-subsystems to access some valid SCSI-device.
At the beginning of the development of this driver, the following approach
was used:
......@@ -251,9 +251,9 @@
lun>0 or to non-existing devices, in order to satisfy the subsystem, if
there are less than 15 SCSI-devices connected. In the case of more than 15
devices, the dynamical mapping goes active. If the get_scsi[][] reports a
device to be existant, but it has no ldn assigned, it gets a ldn out of 7
to 14. The numbers are assigned in cyclic order. Therefore it takes 8
dynamical reassignments on the SCSI-devices, until a certain device
device to be existent, but it has no ldn assigned, it gets an ldn out of 7
to 14. The numbers are assigned in cyclic order, therefore it takes 8
dynamical reassignments on the SCSI-devices until a certain device
loses its ldn again. This assures that dynamical remapping is avoided
during intense I/O between up to 15 SCSI-devices (means pun,lun
combinations). A further advantage of this method is that people who
......@@ -551,7 +551,7 @@
than devices are available, they are assigned to non existing pun,lun
combinations to satisfy the adapter. With this, the dynamical mapping
was possible to implement. (For further info see the text in the
source-code and in the description below. Read the description
source code and in the description below. Read the description
below BEFORE installing this driver on your system!)
2) Changed the name IBMMCA_DRIVER_VERSION to IBMMCA_SCSI_DRIVER_VERSION.
3) The LED-display shows on PS/2-95 no longer the ldn, but the SCSI-ID
......@@ -762,9 +762,9 @@
- Michael Lang
Apr 23, 2000 (v3.2pre1)
1) During a very long time, I collected a huge amount of bugreports from
1) During a very long time, I collected a huge amount of bug reports from
various people, trying really quite different things on their SCSI-
PS/2s. Today, all these bugreports are taken into account and should be
PS/2s. Today, all these bug reports are taken into account and should be
mostly solved. The major topics were:
- Driver crashes during boottime by no obvious reason.
- Driver panics while the midlevel-SCSI-driver is trying to inquire
......@@ -819,7 +819,7 @@
- Michael Lang
July 17, 2000 (v3.2pre8)
A long period of collecting bugreports from all corners of the world
A long period of collecting bug reports from all corners of the world
now lead to the following corrections to the code:
1) SCSI-2 F/W support crashed with a COMMAND ERROR. The reason for this
was that it is possible to disable Fast-SCSI for the external bus.
......@@ -873,7 +873,7 @@
July 26, 2000 (v3.2pre11)
1) I passed a horrible weekend getting mad with NMIs on kernel 2.2.14 and
a model 9595. Asking around in the community, nobody except of me has
seen such errors. Weired, but I am trying to recompile everything on
seen such errors. Weird, but I am trying to recompile everything on
the model 9595. Maybe, as I use a specially modified gcc, that could
cause problems. But, it was not the reason. The true background was,
that the kernel was compiled for i386 and the 9595 has a 486DX-2.
......@@ -886,7 +886,7 @@
alive rotator during boottime. This makes sense, when no monitor is
connected to the system. You can get rid of all display activity, if
you do not use any parameter or just ibmmcascsi=activity, for the
harddrive activity LED, existant on all PS/2, except models 8595-XXX.
harddrive activity LED, existent on all PS/2, except models 8595-XXX.
If no monitor is available, please use ibmmcascsi=display, which works
fine together with the linuxinfo utility for the LED-panel.
- Michael Lang
......@@ -1115,7 +1115,7 @@
If this really happens, do also send e-mail to the maintainer, as
forced detection should be never necessary. Forced detection is in
principal some flaw of the driver adapter detection and goes into
bugreports.
bug reports.
Q: The driver screws up, if it starts to probe SCSI-devices, is there
some way out of it?
A: Yes, that was some recognition problem of the correct SCSI-adapter
......@@ -1172,7 +1172,7 @@
recommended version is 3.2 or later. Here, the F/W support is in
a stable and reliable condition. Wide-addressing is in addition
supported.
Q: I get a Ooops message and something like "killing interrupt".
Q: I get an Oops message and something like "killing interrupt".
A: The reason for this is that the IBM SCSI-subsystem only sends a
termination status back, if some error appeared. In former releases
of the driver, it was not checked, if the termination status block
......@@ -1213,21 +1213,21 @@
problem. Not yet tried, but guessing that it could work. To get this,
set unchecked_isa_dma argument of ibmmca.h from 0 to 1.
5.3 Bugreports
5.3 Bug reports
--------------
If you really find bugs in the sourcecode or the driver will successfully
If you really find bugs in the source code or the driver will successfully
refuse to work on your machine, you should send a bug report to me. The
best for this is to follow the instructions on the WWW-page for this
driver. Fill out the bug-report form, placed on the WWW-page and ship it,
so the bugs can be taken into account with maximum efforts. But, please
do not send bug reports about this driver to Linus Torvalds or Leonard
Zubkoff, as Linus is burried in E-Mail and Leonard is supervising all
Zubkoff, as Linus is buried in E-Mail and Leonard is supervising all
SCSI-drivers and won't have the time left to look inside every single
driver to fix a bug and especially DO NOT send modified code to Linus
Torvalds or Alan J. Cox which has not been checked here!!! They are both
quite burried in E-mail (as me, sometimes, too) and one should first check
quite buried in E-mail (as me, sometimes, too) and one should first check
for problems on my local teststand. Recently, I got a lot of
bugreports for errors in the ibmmca.c code, which I could not imagine, but
bug reports for errors in the ibmmca.c code, which I could not imagine, but
a look inside some Linux-distribution showed me quite often some modified
code, which did no longer work on most other machines than the one of the
modifier. Ok, so now that there is maintenance service available for this
......@@ -1261,7 +1261,7 @@
some e-mail directly, but at least with the same information as required by
the formular.
If you have extensive bugreports, including Ooops messages and
If you have extensive bug reports, including Oops messages and
screen-shots, please feel free to send it directly to the address
of the maintainer, too. The current address of the maintainer is:
......@@ -1318,7 +1318,7 @@
detailed bug reports and ideas for this driver (and his
patience ;-)).
Alan J. Cox
for his bugreports and his bold activities in cross-checking
for his bug reports and his bold activities in cross-checking
the driver-code with his teststand.
7.2 Sponsors & Supporters
......
Documentation/sharedsubtree.txt
浏览文件 @ c00046c2
......@@ -153,6 +153,7 @@ replicas continue to be exactly same.
#include <stdio.h>
#include <stdlib.h>
#include <unistd.h>
#include <string.h>
#include <sys/mount.h>
#include <sys/fsuid.h>
......
Documentation/sound/alsa/soc/DAI.txt
浏览文件 @ c00046c2
......@@ -20,12 +20,12 @@ I2S
===
I2S is a common 4 wire DAI used in HiFi, STB and portable devices. The Tx and
Rx lines are used for audio transmision, whilst the bit clock (BCLK) and
Rx lines are used for audio transmission, whilst the bit clock (BCLK) and
left/right clock (LRC) synchronise the link. I2S is flexible in that either the
controller or CODEC can drive (master) the BCLK and LRC clock lines. Bit clock
usually varies depending on the sample rate and the master system clock
(SYSCLK). LRCLK is the same as the sample rate. A few devices support separate
ADC and DAC LRCLK's, this allows for similtanious capture and playback at
ADC and DAC LRCLK's, this allows for simultaneous capture and playback at
different sample rates.
I2S has several different operating modes:-
......@@ -41,12 +41,12 @@ I2S has several different operating modes:-
PCM
===
PCM is another 4 wire interface, very similar to I2S, that can support a more
PCM is another 4 wire interface, very similar to I2S, which can support a more
flexible protocol. It has bit clock (BCLK) and sync (SYNC) lines that are used
to synchronise the link whilst the Tx and Rx lines are used to transmit and
receive the audio data. Bit clock usually varies depending on sample rate
whilst sync runs at the sample rate. PCM also supports Time Division
Multiplexing (TDM) in that several devices can use the bus similtaniuosly (This
Multiplexing (TDM) in that several devices can use the bus simultaneously (this
is sometimes referred to as network mode).
Common PCM operating modes:-
......
Documentation/sound/alsa/soc/clocking.txt
浏览文件 @ c00046c2
......@@ -2,20 +2,20 @@ Audio Clocking
==============
This text describes the audio clocking terms in ASoC and digital audio in
general. Note: Audio clocking can be complex !
general. Note: Audio clocking can be complex!
Master Clock
------------
Every audio subsystem is driven by a master clock (sometimes refered to as MCLK
Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
or SYSCLK). This audio master clock can be derived from a number of sources
(e.g. crystal, PLL, CPU clock) and is responsible for producing the correct
audio playback and capture sample rates.
Some master clocks (e.g. PLL's and CPU based clocks) are configuarble in that
Some master clocks (e.g. PLL's and CPU based clocks) are configurable in that
their speed can be altered by software (depending on the system use and to save
power). Other master clocks are fixed at at set frequency (i.e. crystals).
power). Other master clocks are fixed at a set frequency (i.e. crystals).
DAI Clocks
......@@ -44,7 +44,7 @@ This relationship depends on the codec or SoC CPU in particular. In general
it's best to configure BCLK to the lowest possible speed (depending on your
rate, number of channels and wordsize) to save on power.
It's also desireable to use the codec (if possible) to drive (or master) the
It's also desirable to use the codec (if possible) to drive (or master) the
audio clocks as it's usually gives more accurate sample rates than the CPU.
......
Documentation/sound/alsa/soc/codec.txt
浏览文件 @ c00046c2
......@@ -19,7 +19,7 @@ Optionally, codec drivers can also provide:-
6) DAPM event handler.
7) DAC Digital mute control.
It's probably best to use this guide in conjuction with the existing codec
It's probably best to use this guide in conjunction with the existing codec
driver code in sound/soc/codecs/
ASoC Codec driver breakdown
......@@ -28,7 +28,7 @@ ASoC Codec driver breakdown
1 - Codec DAI and PCM configuration
-----------------------------------
Each codec driver must have a struct snd_soc_codec_dai to define it's DAI and
PCM's capablities and operations. This struct is exported so that it can be
PCM's capabilities and operations. This struct is exported so that it can be
registered with the core by your machine driver.
e.g.
......@@ -67,7 +67,7 @@ EXPORT_SYMBOL_GPL(wm8731_dai);
2 - Codec control IO
--------------------
The codec can ususally be controlled via an I2C or SPI style interface (AC97
The codec can usually be controlled via an I2C or SPI style interface (AC97
combines control with data in the DAI). The codec drivers will have to provide
functions to read and write the codec registers along with supplying a register
cache:-
......
Documentation/sound/alsa/soc/dapm.txt
浏览文件 @ c00046c2
......@@ -11,7 +11,7 @@ other PM systems.
DAPM is also completely transparent to all user space applications as all power
switching is done within the ASoC core. No code changes or recompiling are
required for user space applications. DAPM makes power switching descisions based
required for user space applications. DAPM makes power switching decisions based
upon any audio stream (capture/playback) activity and audio mixer settings
within the device.
......@@ -38,7 +38,7 @@ There are 4 power domains within DAPM
Enabled and disabled when stream playback/capture is started and
stopped respectively. e.g. aplay, arecord.
All DAPM power switching descisons are made automatically by consulting an audio
All DAPM power switching decisions are made automatically by consulting an audio
routing map of the whole machine. This map is specific to each machine and
consists of the interconnections between every audio component (including
internal codec components). All audio components that effect power are called
......
Documentation/sound/alsa/soc/overview.txt
浏览文件 @ c00046c2
......@@ -2,18 +2,19 @@ ALSA SoC Layer
==============
The overall project goal of the ALSA System on Chip (ASoC) layer is to provide
better ALSA support for embedded system on chip procesors (e.g. pxa2xx, au1x00,
better ALSA support for embedded system-on-chip processors (e.g. pxa2xx, au1x00,
iMX, etc) and portable audio codecs. Currently there is some support in the
kernel for SoC audio, however it has some limitations:-
* Currently, codec drivers are often tightly coupled to the underlying SoC
cpu. This is not ideal and leads to code duplication i.e. Linux now has 4
CPU. This is not ideal and leads to code duplication i.e. Linux now has 4
different wm8731 drivers for 4 different SoC platforms.
* There is no standard method to signal user initiated audio events.
e.g. Headphone/Mic insertion, Headphone/Mic detection after an insertion
event. These are quite common events on portable devices and ofter require
machine specific code to re route audio, enable amps etc after such an event.
* There is no standard method to signal user initiated audio events (e.g.
Headphone/Mic insertion, Headphone/Mic detection after an insertion
event). These are quite common events on portable devices and often require
machine specific code to re-route audio, enable amps, etc., after such an
event.
* Current drivers tend to power up the entire codec when playing
(or recording) audio. This is fine for a PC, but tends to waste a lot of
......@@ -44,7 +45,7 @@ features :-
signals the codec when to change power states.
* Machine specific controls: Allow machines to add controls to the sound card
e.g. volume control for speaker amp.
(e.g. volume control for speaker amp).
To achieve all this, ASoC basically splits an embedded audio system into 3
components :-
......@@ -57,7 +58,7 @@ components :-
interface drivers (e.g. I2S, AC97, PCM) for that platform.
* Machine driver: The machine driver handles any machine specific controls and
audio events. i.e. turing on an amp at start of playback.
audio events (e.g. turning on an amp at start of playback).
Documentation
......
Documentation/sound/alsa/soc/platform.txt
浏览文件 @ c00046c2
......@@ -20,7 +20,7 @@ struct snd_soc_ops {
int (*trigger)(struct snd_pcm_substream *, int);
};
The platform driver exports it's DMA functionailty via struct snd_soc_platform:-
The platform driver exports its DMA functionality via struct snd_soc_platform:-
struct snd_soc_platform {
char *name;
......
Documentation/sound/alsa/soc/pops_clicks.txt
浏览文件 @ c00046c2
......@@ -2,7 +2,7 @@ Audio Pops and Clicks
=====================
Pops and clicks are unwanted audio artifacts caused by the powering up and down
of components within the audio subsystem. This is noticable on PC's when an
of components within the audio subsystem. This is noticeable on PCs when an
audio module is either loaded or unloaded (at module load time the sound card is
powered up and causes a popping noise on the speakers).
......@@ -16,7 +16,7 @@ Minimising Playback Pops and Clicks
===================================
Playback pops in portable audio subsystems cannot be completely eliminated atm,
however future audio codec hardware will have better pop and click supression.
however future audio codec hardware will have better pop and click suppression.
Pops can be reduced within playback by powering the audio components in a
specific order. This order is different for startup and shutdown and follows
some basic rules:-
......@@ -33,7 +33,7 @@ Minimising Capture Pops and Clicks
==================================
Capture artifacts are somewhat easier to get rid as we can delay activating the
ADC until all the pops have occured. This follows similar power rules to
ADC until all the pops have occurred. This follows similar power rules to
playback in that components are powered in a sequence depending upon stream
startup or shutdown.
......
Documentation/spi/pxa2xx
浏览文件 @ c00046c2
PXA2xx SPI on SSP driver HOWTO
PXA2xx SPI on SSP driver HOWTO
===================================================
This a mini howto on the pxa2xx_spi driver. The driver turns a PXA2xx
synchronous serial port into a SPI master controller
......
Documentation/thinkpad-acpi.txt
浏览文件 @ c00046c2
......@@ -1035,7 +1035,7 @@ enable it if necessary to avoid overheating.
An enabled fan in level "auto" may stop spinning if the EC decides the
ThinkPad is cool enough and doesn't need the extra airflow. This is
normal, and the EC will spin the fan up if the varios thermal readings
normal, and the EC will spin the fan up if the various thermal readings
rise too much.
On the X40, this seems to depend on the CPU and HDD temperatures.
......@@ -1203,7 +1203,7 @@ for example:
Enabling debugging output
-------------------------
The module takes a debug paramater which can be used to selectively
The module takes a debug parameter which can be used to selectively
enable various classes of debugging output, for example:
modprobe ibm_acpi debug=0xffff
......
Documentation/usb/usb-serial.txt
浏览文件 @ c00046c2
......@@ -338,7 +338,7 @@ MCT USB Single Port Serial Adapter U232
This driver is for the MCT USB-RS232 Converter (25 pin, Model No.
U232-P25) from Magic Control Technology Corp. (there is also a 9 pin
Model No. U232-P9). More information about this device can be found at
the manufacture's web-site: http://www.mct.com.tw.
the manufacturer's web-site: http://www.mct.com.tw.
The driver is generally working, though it still needs some more testing.
It is derived from the Belkin USB Serial Adapter F5U103 driver and its
......
arch/alpha/kernel/err_marvel.c
浏览文件 @ c00046c2
......@@ -1082,7 +1082,7 @@ marvel_machine_check(u64 vector, u64 la_ptr)
}
/*
* A system event or error has occured, handle it here.
* A system event or error has occurred, handle it here.
*
* Any errors in the logout frame have already been cleared by the
* PALcode, so just parse it.
......
arch/alpha/kernel/err_titan.c
浏览文件 @ c00046c2
......@@ -591,7 +591,7 @@ privateer_process_680_frame(struct el_common *mchk_header, int print)
(struct el_PRIVATEER_envdata_mcheck *)
((unsigned long)mchk_header + mchk_header->sys_offset);
/* TODO - catagorize errors, for now, no error */
/* TODO - categorize errors, for now, no error */
if (!print)
return status;
......
arch/alpha/kernel/osf_sys.c
浏览文件 @ c00046c2
......@@ -715,7 +715,7 @@ osf_setsysinfo(unsigned long op, void __user *buffer, unsigned long nbytes,
/*
* Alpha Architecture Handbook 4.7.7.3:
* To be fully IEEE compiant, we must track the current IEEE
* exception state in software, because spurrious bits can be
* exception state in software, because spurious bits can be
* set in the trap shadow of a software-complete insn.
*/
......
arch/alpha/kernel/smp.c
浏览文件 @ c00046c2
......@@ -439,7 +439,6 @@ setup_smp(void)
((char *)cpubase + i*hwrpb->processor_size);
if ((cpu->flags & 0x1cc) == 0x1cc) {
smp_num_probed++;
/* Assume here that "whami" == index */
cpu_set(i, cpu_present_map);
cpu->pal_revision = boot_cpu_palrev;
}
......
arch/alpha/kernel/sys_alcor.c
浏览文件 @ c00046c2
......@@ -138,7 +138,7 @@ alcor_init_irq(void)
for (i = 16; i < 48; ++i) {
/* On Alcor, at least, lines 20..30 are not connected
and can generate spurrious interrupts if we turn them
and can generate spurious interrupts if we turn them
on while IRQ probing. */
if (i >= 16+20 && i <= 16+30)
continue;
......
arch/alpha/kernel/sys_sio.c
浏览文件 @ c00046c2
......@@ -78,7 +78,7 @@ alphabook1_init_arch(void)
* example, sound boards seem to like using IRQ 9.
*
* This is NOT how we should do it. PIRQ0-X should have
* their own IRQ's, the way intel uses the IO-APIC irq's.
* their own IRQs, the way intel uses the IO-APIC IRQs.
*/
static void __init
......
arch/alpha/lib/checksum.c
浏览文件 @ c00046c2
......@@ -5,7 +5,7 @@
* in an architecture-specific manner due to speed..
* Comments in other versions indicate that the algorithms are from RFC1071
*
* accellerated versions (and 21264 assembly versions ) contributed by
* accelerated versions (and 21264 assembly versions ) contributed by
* Rick Gorton <rick.gorton@alpha-processor.com>
*/
......
arch/alpha/lib/csum_partial_copy.c
浏览文件 @ c00046c2
......@@ -2,7 +2,7 @@
* csum_partial_copy - do IP checksumming and copy
*
* (C) Copyright 1996 Linus Torvalds
* accellerated versions (and 21264 assembly versions ) contributed by
* accelerated versions (and 21264 assembly versions ) contributed by
* Rick Gorton <rick.gorton@alpha-processor.com>
*
* Don't look at this too closely - you'll go mad. The things
......
arch/alpha/mm/init.c
浏览文件 @ c00046c2
......@@ -235,7 +235,7 @@ callback_init(void * kernel_end)
unsigned long pfn = crb->map[i].pa >> PAGE_SHIFT;
crb->map[i].va = vaddr;
for (j = 0; j < crb->map[i].count; ++j) {
/* Newer console's (especially on larger
/* Newer consoles (especially on larger
systems) may require more pages of
PTEs. Grab additional pages as needed. */
if (pmd != pmd_offset(pgd, vaddr)) {
......
arch/alpha/oprofile/op_impl.h
浏览文件 @ c00046c2
......@@ -38,7 +38,7 @@ struct op_register_config {
unsigned long need_reset;
};
/* Per-architecture configury and hooks. */
/* Per-architecture configuration and hooks. */
struct op_axp_model {
void (*reg_setup) (struct op_register_config *,
struct op_counter_config *,
......
arch/arm/Kconfig
浏览文件 @ c00046c2
......@@ -851,7 +851,7 @@ config KEXEC
help
kexec is a system call that implements the ability to shutdown your
current kernel, and to start another kernel. It is like a reboot
but it is indepedent of the system firmware. And like a reboot
but it is independent of the system firmware. And like a reboot
you can start any kernel with it, not just Linux.
It is an ongoing process to be certain the hardware in a machine
......
arch/arm/mach-at91/gpio.c
浏览文件 @ c00046c2
......@@ -439,7 +439,7 @@ void __init at91_gpio_irq_setup(void)
for (i = 0; i < 32; i++, pin++) {
/*
* Can use the "simple" and not "edge" handler since it's
* shorter, and the AIC handles interupts sanely.
* shorter, and the AIC handles interrupts sanely.
*/
set_irq_chip(pin, &gpio_irqchip);
set_irq_handler(pin, handle_simple_irq);
......
arch/arm/mach-omap1/irq.c
浏览文件 @ c00046c2
......@@ -5,7 +5,7 @@
*
* Copyright (C) 2004 Nokia Corporation
* Written by Tony Lindgren <tony@atomide.com>
* Major cleanups by Juha Yrjl <juha.yrjola@nokia.com>
* Major cleanups by Juha Yrjölä <juha.yrjola@nokia.com>
*
* Completely re-written to support various OMAP chips with bank specific
* interrupt handlers.
......
arch/arm/mach-omap2/timer-gp.c
浏览文件 @ c00046c2
......@@ -5,7 +5,7 @@
*
* Copyright (C) 2005 Nokia Corporation
* Author: Paul Mundt <paul.mundt@nokia.com>
* Juha Yrjl <juha.yrjola@nokia.com>
* Juha Yrjölä <juha.yrjola@nokia.com>
* OMAP Dual-mode timer framework support by Timo Teras
*
* Some parts based off of TI's 24xx code:
......
arch/arm/mach-s3c2410/clock.c
浏览文件 @ c00046c2
......@@ -238,7 +238,7 @@ int __init s3c2410_baseclk_add(void)
}
/* We must be careful disabling the clocks we are not intending to
* be using at boot time, as subsytems such as the LCD which do
* be using at boot time, as subsystems such as the LCD which do
* their own DMA requests to the bus can cause the system to lockup
* if they where in the middle of requesting bus access.
*
......
arch/arm/mach-s3c2412/clock.c
浏览文件 @ c00046c2
......@@ -689,7 +689,7 @@ int __init s3c2412_baseclk_add(void)
}
/* We must be careful disabling the clocks we are not intending to
* be using at boot time, as subsytems such as the LCD which do
* be using at boot time, as subsystems such as the LCD which do
* their own DMA requests to the bus can cause the system to lockup
* if they where in the middle of requesting bus access.
*
......
arch/arm/mach-s3c2443/clock.c
浏览文件 @ c00046c2
......@@ -1005,7 +1005,7 @@ void __init s3c2443_init_clocks(int xtal)
}
/* We must be careful disabling the clocks we are not intending to
* be using at boot time, as subsytems such as the LCD which do
* be using at boot time, as subsystems such as the LCD which do
* their own DMA requests to the bus can cause the system to lockup
* if they where in the middle of requesting bus access.
*
......
arch/arm/nwfpe/fpopcode.h
浏览文件 @ c00046c2
......@@ -78,11 +78,11 @@ TABLE 1
+-------------------------+---+---+---------+---------+
| Precision | u | v | FPSR.EP | length |
+-------------------------+---+---+---------+---------+
| Single | 0 0 | x | 1 words |
| Double | 1 1 | x | 2 words |
| Extended | 1 1 | x | 3 words |
| Packed decimal | 1 1 | 0 | 3 words |
| Expanded packed decimal | 1 1 | 1 | 4 words |
| Single | 0 | 0 | x | 1 words |
| Double | 1 | 1 | x | 2 words |
| Extended | 1 | 1 | x | 3 words |
| Packed decimal | 1 | 1 | 0 | 3 words |
| Expanded packed decimal | 1 | 1 | 1 | 4 words |
+-------------------------+---+---+---------+---------+
Note: x = don't care
*/
......@@ -92,10 +92,10 @@ TABLE 2
+---+---+---------------------------------+
| w | x | Number of registers to transfer |
+---+---+---------------------------------+
| 0 1 | 1 |
| 1 0 | 2 |
| 1 1 | 3 |
| 0 0 | 4 |
| 0 | 1 | 1 |
| 1 | 0 | 2 |
| 1 | 1 | 3 |
| 0 | 0 | 4 |
+---+---+---------------------------------+
*/
......@@ -156,10 +156,10 @@ TABLE 5
+-------------------------+---+---+
| Rounding Precision | e | f |
+-------------------------+---+---+
| IEEE Single precision | 0 0 |
| IEEE Double precision | 0 1 |
| IEEE Extended precision | 1 0 |
| undefined (trap) | 1 1 |
| IEEE Single precision | 0 | 0 |
| IEEE Double precision | 0 | 1 |
| IEEE Extended precision | 1 | 0 |
| undefined (trap) | 1 | 1 |
+-------------------------+---+---+
*/
......@@ -168,10 +168,10 @@ TABLE 5
+---------------------------------+---+---+
| Rounding Mode | g | h |
+---------------------------------+---+---+
| Round to nearest (default) | 0 0 |
| Round toward plus infinity | 0 1 |
| Round toward negative infinity | 1 0 |
| Round toward zero | 1 1 |
| Round to nearest (default) | 0 | 0 |
| Round toward plus infinity | 0 | 1 |
| Round toward negative infinity | 1 | 0 |
| Round toward zero | 1 | 1 |
+---------------------------------+---+---+
*/
......
arch/arm/plat-omap/dma.c
浏览文件 @ c00046c2
......@@ -2,7 +2,7 @@
* linux/arch/arm/plat-omap/dma.c
*
* Copyright (C) 2003 Nokia Corporation
* Author: Juha Yrjl <juha.yrjola@nokia.com>
* Author: Juha Yrjölä <juha.yrjola@nokia.com>
* DMA channel linking for 1610 by Samuel Ortiz <samuel.ortiz@nokia.com>
* Graphics DMA and LCD DMA graphics tranformations
* by Imre Deak <imre.deak@nokia.com>
......
arch/arm/plat-omap/gpio.c
浏览文件 @ c00046c2
......@@ -4,7 +4,7 @@
* Support functions for OMAP GPIO
*
* Copyright (C) 2003-2005 Nokia Corporation
* Written by Juha Yrjl <juha.yrjola@nokia.com>
* Written by Juha Yrjölä <juha.yrjola@nokia.com>
*
* This program is free software; you can redistribute it and/or modify
* it under the terms of the GNU General Public License version 2 as
......
arch/avr32/Kconfig
浏览文件 @ c00046c2
......@@ -189,7 +189,7 @@ config CMDLINE
endmenu
menu "Power managment options"
menu "Power management options"
menu "CPU Frequency scaling"
......
arch/blackfin/Kconfig
浏览文件 @ c00046c2
......@@ -613,85 +613,86 @@ config I_ENTRY_L1
bool "Locate interrupt entry code in L1 Memory"
default y
help
If enabled interrupt entry code (STORE/RESTORE CONTEXT) is linked
into L1 instruction memory.(less latency)
If enabled, interrupt entry code (STORE/RESTORE CONTEXT) is linked
into L1 instruction memory. (less latency)
config EXCPT_IRQ_SYSC_L1
bool "Locate entire ASM lowlevel excepetion / interrupt - Syscall and CPLB handler code in L1 Memory"
bool "Locate entire ASM lowlevel exception / interrupt - Syscall and CPLB handler code in L1 Memory"
default y
help
If enabled entire ASM lowlevel exception and interrupt entry code (STORE/RESTORE CONTEXT) is linked
into L1 instruction memory.(less latency)
If enabled, the entire ASM lowlevel exception and interrupt entry code
(STORE/RESTORE CONTEXT) is linked into L1 instruction memory.
(less latency)
config DO_IRQ_L1
bool "Locate frequently called do_irq dispatcher function in L1 Memory"
default y
help
If enabled frequently called do_irq dispatcher function is linked
into L1 instruction memory.(less latency)
If enabled, the frequently called do_irq dispatcher function is linked
into L1 instruction memory. (less latency)
config CORE_TIMER_IRQ_L1
bool "Locate frequently called timer_interrupt() function in L1 Memory"
default y
help
If enabled frequently called timer_interrupt() function is linked
into L1 instruction memory.(less latency)
If enabled, the frequently called timer_interrupt() function is linked
into L1 instruction memory. (less latency)
config IDLE_L1
bool "Locate frequently idle function in L1 Memory"
default y
help
If enabled frequently called idle function is linked
into L1 instruction memory.(less latency)
If enabled, the frequently called idle function is linked
into L1 instruction memory. (less latency)
config SCHEDULE_L1
bool "Locate kernel schedule function in L1 Memory"
default y
help
If enabled frequently called kernel schedule is linked
into L1 instruction memory.(less latency)
If enabled, the frequently called kernel schedule is linked
into L1 instruction memory. (less latency)
config ARITHMETIC_OPS_L1
bool "Locate kernel owned arithmetic functions in L1 Memory"
default y
help
If enabled arithmetic functions are linked
into L1 instruction memory.(less latency)
If enabled, arithmetic functions are linked
into L1 instruction memory. (less latency)
config ACCESS_OK_L1
bool "Locate access_ok function in L1 Memory"
default y
help
If enabled access_ok function is linked
into L1 instruction memory.(less latency)
If enabled, the access_ok function is linked
into L1 instruction memory. (less latency)
config MEMSET_L1
bool "Locate memset function in L1 Memory"
default y
help
If enabled memset function is linked
into L1 instruction memory.(less latency)
If enabled, the memset function is linked
into L1 instruction memory. (less latency)
config MEMCPY_L1
bool "Locate memcpy function in L1 Memory"
default y
help
If enabled memcpy function is linked
into L1 instruction memory.(less latency)
If enabled, the memcpy function is linked
into L1 instruction memory. (less latency)
config SYS_BFIN_SPINLOCK_L1
bool "Locate sys_bfin_spinlock function in L1 Memory"
default y
help
If enabled sys_bfin_spinlock function is linked
into L1 instruction memory.(less latency)
If enabled, sys_bfin_spinlock function is linked
into L1 instruction memory. (less latency)
config IP_CHECKSUM_L1
bool "Locate IP Checksum function in L1 Memory"
default n
help
If enabled IP Checksum function is linked
into L1 instruction memory.(less latency)
If enabled, the IP Checksum function is linked
into L1 instruction memory. (less latency)
config CACHELINE_ALIGNED_L1
bool "Locate cacheline_aligned data to L1 Data Memory"
......@@ -699,24 +700,24 @@ config CACHELINE_ALIGNED_L1
default n if BF54x
depends on !BF531
help
If enabled cacheline_anligned data is linked
into L1 data memory.(less latency)
If enabled, cacheline_anligned data is linked
into L1 data memory. (less latency)
config SYSCALL_TAB_L1
bool "Locate Syscall Table L1 Data Memory"
default n
depends on !BF531
help
If enabled the Syscall LUT is linked
into L1 data memory.(less latency)
If enabled, the Syscall LUT is linked
into L1 data memory. (less latency)
config CPLB_SWITCH_TAB_L1
bool "Locate CPLB Switch Tables L1 Data Memory"
default n
depends on !BF531
help
If enabled the CPLB Switch Tables are linked
into L1 data memory.(less latency)
If enabled, the CPLB Switch Tables are linked
into L1 data memory. (less latency)
endmenu
......@@ -1029,13 +1030,13 @@ config DEBUG_HWERR
from.
config DEBUG_ICACHE_CHECK
bool "Check Instruction cache coherancy"
bool "Check Instruction cache coherency"
depends on DEBUG_KERNEL
depends on DEBUG_HWERR
help
Say Y here if you are getting wierd unexplained errors. This will
ensure that icache is what SDRAM says it should be, by doing a
byte wise comparision between SDRAM and instruction cache. This
Say Y here if you are getting weird unexplained errors. This will
ensure that icache is what SDRAM says it should be by doing a
byte wise comparison between SDRAM and instruction cache. This
also relocates the irq_panic() function to L1 memory, (which is
un-cached).
......
arch/cris/arch-v10/Kconfig
浏览文件 @ c00046c2
......@@ -182,7 +182,7 @@ config ETRAX_LED7G
set this to same as CONFIG_ETRAX_LED1G (normally 2).
config ETRAX_LED8Y
int "Eigth yellow LED bit"
int "Eighth yellow LED bit"
depends on ETRAX_CSP0_LEDS
default "2"
help
......
arch/cris/arch-v10/boot/compressed/misc.c
浏览文件 @ c00046c2
......@@ -8,7 +8,7 @@
*
* malloc by Hannu Savolainen 1993 and Matthias Urlichs 1994
* puts by Nick Holloway 1993, better puts by Martin Mares 1995
* adoptation for Linux/CRIS Axis Communications AB, 1999
* adaptation for Linux/CRIS Axis Communications AB, 1999
*
*/
......
arch/cris/arch-v10/drivers/pcf8563.c
浏览文件 @ c00046c2
......@@ -4,7 +4,7 @@
* From Phillips' datasheet:
*
* The PCF8563 is a CMOS real-time clock/calendar optimized for low power
* consumption. A programmable clock output, interupt output and voltage
* consumption. A programmable clock output, interrupt output and voltage
* low detector are also provided. All address and data are transferred
* serially via two-line bidirectional I2C-bus. Maximum bus speed is
* 400 kbits/s. The built-in word address register is incremented
......
arch/cris/arch-v10/kernel/debugport.c
浏览文件 @ c00046c2
......@@ -83,7 +83,7 @@
*
* Revision 1.4 2002/11/19 14:35:24 starvik
* Changes from linux 2.4
* Changed struct initializer syntax to the currently prefered notation
* Changed struct initializer syntax to the currently preferred notation
*
* Revision 1.3 2002/11/06 09:47:03 starvik
* Modified for new interrupt macros
......
arch/cris/arch-v10/kernel/entry.S
浏览文件 @ c00046c2
......@@ -97,7 +97,7 @@
*
* Revision 1.36 2001/11/22 13:36:36 bjornw
* * In ret_from_intr, check regs->dccr for usermode reentrance instead of
* DCCR explicitely (because the latter might not reflect current reality)
* DCCR explicitly (because the latter might not reflect current reality)
* * In mmu_bus_fault, set $r9 _after_ calling the C-code instead of before
* since $r9 is call-clobbered and is potentially needed afterwards
*
......
arch/cris/arch-v10/kernel/fasttimer.c
浏览文件 @ c00046c2
......@@ -84,7 +84,7 @@
* with time based on jiffies and *R_TIMER0_DATA, uses a table
* for fast conversion of timer value to microseconds.
* (Much faster the standard do_gettimeofday() and we don't really
* wan't to use the true time - we wan't the "uptime" so timers don't screw up
* want to use the true time - we want the "uptime" so timers don't screw up
* when we change the time.
* TODO: Add efficient support for continuous timers as well.
*
......
arch/cris/arch-v10/kernel/irq.c
浏览文件 @ c00046c2
......@@ -169,7 +169,7 @@ init_IRQ(void)
for (i = 0; i < 256; i++)
etrax_irv->v[i] = weird_irq;
/* Initialize IRQ handler descriptiors. */
/* Initialize IRQ handler descriptors. */
for(i = 2; i < NR_IRQS; i++) {
irq_desc[i].chip = &crisv10_irq_type;
set_int_vector(i, interrupt[i]);
......
arch/cris/arch-v10/kernel/kgdb.c
浏览文件 @ c00046c2
......@@ -959,7 +959,7 @@ stub_is_stopped(int sigval)
/* Send register contents. We probably only need to send the
* PC, frame pointer and stack pointer here. Other registers will be
* explicitely asked for. But for now, send all.
* explicitly asked for. But for now, send all.
*/
for (regno = R0; regno <= USP; regno++) {
......
arch/cris/arch-v10/kernel/process.c
浏览文件 @ c00046c2
......@@ -64,7 +64,7 @@ void hard_reset_now (void)
#if defined(CONFIG_ETRAX_WATCHDOG) && !defined(CONFIG_SVINTO_SIM)
cause_of_death = 0xbedead;
#else
/* Since we dont plan to keep on reseting the watchdog,
/* Since we dont plan to keep on resetting the watchdog,
the key can be arbitrary hence three */
*R_WATCHDOG = IO_FIELD(R_WATCHDOG, key, 3) |
IO_STATE(R_WATCHDOG, enable, start);
......
arch/cris/arch-v10/kernel/shadows.c
浏览文件 @ c00046c2
......@@ -20,7 +20,7 @@ unsigned long r_timer_ctrl_shadow;
* These are only usable if there actually IS a latch connected
* to the corresponding external chip-select pin.
*
* A common usage is that CSP0 controls LED's and CSP4 video chips.
* A common usage is that CSP0 controls LEDs and CSP4 video chips.
*/
unsigned long port_cse1_shadow;
......
arch/cris/arch-v10/lib/dram_init.S
浏览文件 @ c00046c2
......@@ -40,7 +40,7 @@
* Copy warning from head.S about r8 and r9
*
* Revision 1.7 2001/04/18 12:05:39 bjornw
* Fixed comments, and explicitely include config.h to be sure its there
* Fixed comments, and explicitly include config.h to be sure its there
*
* Revision 1.6 2001/04/10 06:20:16 starvik
* Delay should be 200us, not 200ns
......@@ -66,7 +66,7 @@
*/
/* Just to be certain the config file is included, we include it here
* explicitely instead of depending on it being included in the file that
* explicitly instead of depending on it being included in the file that
* uses this code.
*/
......
arch/cris/arch-v10/lib/string.c
浏览文件 @ c00046c2
......@@ -41,7 +41,7 @@ void *memcpy(void *pdst,
Make sure the compiler is able to make something useful of this.
As it is now: r10 -> r13; r11 -> r11 (nop); r12 -> r12 (nop).
If gcc was allright, it really would need no temporaries, and no
If gcc was alright, it really would need no temporaries, and no
stack space to save stuff on. */
register void *return_dst __asm__ ("r10") = pdst;
......
arch/cris/arch-v10/lib/usercopy.c
浏览文件 @ c00046c2
......@@ -38,7 +38,7 @@ __copy_user (void __user *pdst, const void *psrc, unsigned long pn)
As it is now: r10 -> r13; r11 -> r11 (nop); r12 -> r12 (nop).
FIXME: Comment for old gcc version. Check.
If gcc was allright, it really would need no temporaries, and no
If gcc was alright, it really would need no temporaries, and no
stack space to save stuff on. */
register char *dst __asm__ ("r13") = pdst;
......@@ -200,7 +200,7 @@ __copy_user_zeroing (void __user *pdst, const void *psrc, unsigned long pn)
As it is now: r10 -> r13; r11 -> r11 (nop); r12 -> r12 (nop).
FIXME: Comment for old gcc version. Check.
If gcc was allright, it really would need no temporaries, and no
If gcc was alright, it really would need no temporaries, and no
stack space to save stuff on. */
register char *dst __asm__ ("r13") = pdst;
......@@ -380,7 +380,7 @@ __do_clear_user (void __user *pto, unsigned long pn)
As it is now: r10 -> r13; r11 -> r11 (nop); r12 -> r12 (nop).
FIXME: Comment for old gcc version. Check.
If gcc was allright, it really would need no temporaries, and no
If gcc was alright, it really would need no temporaries, and no
stack space to save stuff on. */
register char *dst __asm__ ("r13") = pto;
......
arch/cris/arch-v32/boot/compressed/misc.c
浏览文件 @ c00046c2
......@@ -8,7 +8,7 @@
*
* malloc by Hannu Savolainen 1993 and Matthias Urlichs 1994
* puts by Nick Holloway 1993, better puts by Martin Mares 1995
* adoptation for Linux/CRIS Axis Communications AB, 1999
* adaptation for Linux/CRIS Axis Communications AB, 1999
*
*/
......@@ -151,7 +151,7 @@ serout(const char *s, reg_scope_instances regi_ser)
do {
rs = REG_RD(ser, regi_ser, rs_stat_din);
}
while (!rs.tr_rdy);/* Wait for tranceiver. */
while (!rs.tr_rdy);/* Wait for transceiver. */
REG_WR(ser, regi_ser, rw_dout, dout);
}
......@@ -264,7 +264,7 @@ serial_setup(reg_scope_instances regi_ser)
tr_ctrl.stop_bits = 1; /* 2 stop bits. */
/*
* The baudrate setup is a bit fishy, but in the end the tranceiver is
* The baudrate setup is a bit fishy, but in the end the transceiver is
* set to 4800 and the receiver to 115200. The magic value is
* 29.493 MHz.
*/
......
arch/cris/arch-v32/drivers/axisflashmap.c
浏览文件 @ c00046c2
......@@ -205,7 +205,7 @@ static struct mtd_info *probe_cs(struct map_info *map_cs)
/*
* Probe each chip select individually for flash chips. If there are chips on
* both cse0 and cse1, the mtd_info structs will be concatenated to one struct
* so that MTD partitions can cross chip boundries.
* so that MTD partitions can cross chip boundaries.
*
* The only known restriction to how you can mount your chips is that each
* chip select must hold similar flash chips. But you need external hardware
......
arch/cris/arch-v32/drivers/i2c.c
浏览文件 @ c00046c2
......@@ -275,7 +275,7 @@ i2c_getack(void)
ack = 0;
i2c_delay(CLOCK_HIGH_TIME/2);
if(!ack){
if(!i2c_getbit()) /* receiver pulld SDA low */
if(!i2c_getbit()) /* receiver pulled SDA low */
ack = 1;
i2c_delay(CLOCK_HIGH_TIME/2);
}
......
arch/cris/arch-v32/drivers/nandflash.c
浏览文件 @ c00046c2
......@@ -138,7 +138,7 @@ struct mtd_info* __init crisv32_nand_flash_probe (void)
/* Enable the following for a flash based bad block table */
this->options = NAND_USE_FLASH_BBT;
/* Scan to find existance of the device */
/* Scan to find existence of the device */
if (nand_scan (crisv32_mtd, 1)) {
err = -ENXIO;
goto out_ior;
......
arch/cris/arch-v32/drivers/pcf8563.c
浏览文件 @ c00046c2
......@@ -4,7 +4,7 @@
* From Phillips' datasheet:
*
* The PCF8563 is a CMOS real-time clock/calendar optimized for low power
* consumption. A programmable clock output, interupt output and voltage
* consumption. A programmable clock output, interrupt output and voltage
* low detector are also provided. All address and data are transferred
* serially via two-line bidirectional I2C-bus. Maximum bus speed is
* 400 kbits/s. The built-in word address register is incremented
......
arch/cris/arch-v32/kernel/fasttimer.c
浏览文件 @ c00046c2
......@@ -97,7 +97,7 @@
* with time based on jiffies and *R_TIMER0_DATA, uses a table
* for fast conversion of timer value to microseconds.
* (Much faster the standard do_gettimeofday() and we don't really
* wan't to use the true time - we wan't the "uptime" so timers don't screw up
* want to use the true time - we want the "uptime" so timers don't screw up
* when we change the time.
* TODO: Add efficient support for continuous timers as well.
*
......
arch/cris/arch-v32/kernel/irq.c
浏览文件 @ c00046c2
......@@ -140,7 +140,7 @@ block_irq(int irq, int cpu)
spin_lock_irqsave(&irq_lock, flags);
intr_mask = REG_RD_INT(intr_vect, irq_regs[cpu], rw_mask);
/* Remember; 1 let thru, 0 block. */
/* Remember; 1 let through, 0 block. */
intr_mask &= ~(1 << (irq - FIRST_IRQ));
REG_WR_INT(intr_vect, irq_regs[cpu], rw_mask, intr_mask);
......@@ -156,7 +156,7 @@ unblock_irq(int irq, int cpu)
spin_lock_irqsave(&irq_lock, flags);
intr_mask = REG_RD_INT(intr_vect, irq_regs[cpu], rw_mask);
/* Remember; 1 let thru, 0 block. */
/* Remember; 1 let through, 0 block. */
intr_mask |= (1 << (irq - FIRST_IRQ));
REG_WR_INT(intr_vect, irq_regs[cpu], rw_mask, intr_mask);
......@@ -308,7 +308,7 @@ crisv32_do_multiple(struct pt_regs* regs)
*/
irq_enter();
/* Get which IRQs that happend. */
/* Get which IRQs that happened. */
masked = REG_RD_INT(intr_vect, irq_regs[cpu], r_masked_vect);
/* Calculate new IRQ mask with these IRQs disabled. */
......@@ -366,7 +366,7 @@ init_IRQ(void)
for (i = 0; i < 256; i++)
etrax_irv->v[i] = weird_irq;
/* Point all IRQ's to bad handlers. */
/* Point all IRQs to bad handlers. */
for (i = FIRST_IRQ, j = 0; j < NR_IRQS; i++, j++) {
irq_desc[j].chip = &crisv32_irq_type;
set_exception_vector(i, interrupt[j]);
......
arch/cris/arch-v32/kernel/process.c
浏览文件 @ c00046c2
......@@ -162,7 +162,7 @@ copy_thread(int nr, unsigned long clone_flags, unsigned long usp,
/* Put the switch stack right below the pt_regs. */
swstack = ((struct switch_stack *) childregs) - 1;
/* Paramater to ret_from_sys_call. 0 is don't restart the syscall. */
/* Parameter to ret_from_sys_call. 0 is don't restart the syscall. */
swstack->r9 = 0;
/*
......
arch/cris/arch-v32/kernel/signal.c
浏览文件 @ c00046c2
......@@ -347,7 +347,7 @@ get_sigframe(struct k_sigaction *ka, struct pt_regs * regs, size_t frame_size)
/* Grab and setup a signal frame.
*
* Basically a lot of state-info is stacked, and arranged for the
* user-mode program to return to the kernel using either a trampiline
* user-mode program to return to the kernel using either a trampoline
* which performs the syscall sigreturn(), or a provided user-mode
* trampoline.
*/
......@@ -641,7 +641,7 @@ ugdb_trap_user(struct thread_info *ti, int sig)
user_regs(ti)->spc = 0;
}
/* FIXME: Filter out false h/w breakpoint hits (i.e. EDA
not withing any configured h/w breakpoint range). Synchronize with
not within any configured h/w breakpoint range). Synchronize with
what already exists for kernel debugging. */
if (((user_regs(ti)->exs & 0xff00) >> 8) == BREAK_8_INTR_VECT) {
/* Break 8: subtract 2 from ERP unless in a delay slot. */
......
arch/cris/arch-v32/kernel/smp.c
浏览文件 @ c00046c2
......@@ -142,7 +142,7 @@ smp_boot_one_cpu(int cpuid)
return -1;
}
/* Secondary CPUs starts uing C here. Here we need to setup CPU
/* Secondary CPUs starts using C here. Here we need to setup CPU
* specific stuff such as the local timer and the MMU. */
void __init smp_callin(void)
{
......
arch/cris/arch-v32/kernel/time.c
浏览文件 @ c00046c2
......@@ -99,7 +99,7 @@ unsigned long do_slow_gettimeoffset(void)
/* From timer MDS describing the hardware watchdog:
* 4.3.1 Watchdog Operation
* The watchdog timer is an 8-bit timer with a configurable start value.
* Once started the whatchdog counts downwards with a frequency of 763 Hz
* Once started the watchdog counts downwards with a frequency of 763 Hz
* (100/131072 MHz). When the watchdog counts down to 1, it generates an
* NMI (Non Maskable Interrupt), and when it counts down to 0, it resets the
* chip.
......
arch/cris/arch-v32/kernel/traps.c
浏览文件 @ c00046c2
......@@ -105,7 +105,7 @@ show_registers(struct pt_regs *regs)
/*
* This gets called from entry.S when the watchdog has bitten. Show something
* similiar to an Oops dump, and if the kernel if configured to be a nice doggy;
* similar to an Oops dump, and if the kernel is configured to be a nice doggy;
* halt instead of reboot.
*/
void
......
arch/cris/arch-v32/lib/dram_init.S
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/arch-v32/lib/string.c
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/arch-v32/lib/usercopy.c
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/arch-v32/mm/tlb.c
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/kernel/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/mm/fault.c
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/mm/init.c
浏览文件 @ c00046c2
此差异已折叠。
arch/cris/mm/tlb.c
浏览文件 @ c00046c2
此差异已折叠。
arch/frv/kernel/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/frv/kernel/semaphore.c
浏览文件 @ c00046c2
此差异已折叠。
arch/frv/kernel/time.c
浏览文件 @ c00046c2
此差异已折叠。
arch/h8300/Kconfig.debug
浏览文件 @ c00046c2
此差异已折叠。
arch/h8300/kernel/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/h8300/kernel/time.c
浏览文件 @ c00046c2
此差异已折叠。
arch/h8300/kernel/traps.c
浏览文件 @ c00046c2
此差异已折叠。
arch/h8300/platform/h8s/ints.c
浏览文件 @ c00046c2
此差异已折叠。
arch/h8300/platform/h8s/ints_h8s.c
浏览文件 @ c00046c2
此差异已折叠。
arch/i386/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
arch/ia64/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
arch/m32r/kernel/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m32r/kernel/signal.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m32r/kernel/smp.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m32r/kernel/smpboot.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m32r/kernel/sys_m32r.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/amiga/pcmcia.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/CHANGES
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/MISC
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/README
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/TEST.DOC
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/fplsp.doc
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/fpsp.doc
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/fskeleton.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/ilsp.doc
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/iskeleton.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/isp.doc
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/os.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/fplsp.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/fpsp.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/ftest.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/ilsp.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/isp.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/itest.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/ifpsp060/src/pfpsp.S
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/mac/config.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/mac/iop.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/mac/oss.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/mac/via.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/math-emu/fp_log.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/q40/q40ints.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/sun3/mmu_emu.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68k/tools/amiga/dmesg.c
浏览文件 @ c00046c2
此差异已折叠。
arch/m68knommu/platform/5307/pit.c
浏览文件 @ c00046c2
此差异已折叠。
arch/mips/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
arch/mips/kernel/module.c
浏览文件 @ c00046c2
此差异已折叠。
arch/mips/pci/pci-excite.c
浏览文件 @ c00046c2
此差异已折叠。
arch/mips/sni/pcimt.c
浏览文件 @ c00046c2
此差异已折叠。
arch/powerpc/kernel/cpu_setup_6xx.S
浏览文件 @ c00046c2
此差异已折叠。
arch/powerpc/kernel/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/powerpc/kernel/l2cr_6xx.S
浏览文件 @ c00046c2
此差异已折叠。
arch/powerpc/platforms/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
arch/sh64/kernel/pci_sh5.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
arch/um/drivers/line.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/drivers/null.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/drivers/stderr_console.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/kernel/gmon_syms.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/kernel/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/kernel/ptrace.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/sys-i386/bug.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/sys-i386/tls.c
浏览文件 @ c00046c2
此差异已折叠。
arch/um/sys-x86_64/bug.c
浏览文件 @ c00046c2
此差异已折叠。
arch/v850/kernel/me2.c
浏览文件 @ c00046c2
此差异已折叠。
arch/v850/kernel/rte_mb_a_pci.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/boot/compressed/misc_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/boot/compressed/misc_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/acpi/boot.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/apic_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/apm_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/amd.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/centaur.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/common.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/cyrix.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/cyrix.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/generic.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/cpu/mtrr/main.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/e820_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/hpet.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/i8253.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/io_apic_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/io_apic_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/mce_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/mpparse_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/ptrace_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/setup_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/signal_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/signal_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/smp_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/smpboot_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/smpboot_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/summit_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/suspend_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/traps_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/tsc_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/kernel/vsyscall_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mach-default/setup.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mach-generic/default.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mach-generic/probe.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mach-voyager/voyager_smp.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mm/boot_ioremap_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mm/discontig_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mm/fault_32.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mm/fault_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/mm/srat_64.c
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/oprofile/op_x86_model.h
浏览文件 @ c00046c2
此差异已折叠。
arch/x86/pci/irq.c
浏览文件 @ c00046c2
此差异已折叠。
arch/xtensa/platform-iss/network.c
浏览文件 @ c00046c2
此差异已折叠。
block/elevator.c
浏览文件 @ c00046c2
此差异已折叠。
crypto/api.c
浏览文件 @ c00046c2
此差异已折叠。
crypto/fcrypt.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/acpi/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/ahci.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/libata-sff.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_cmd64x.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_cs5530.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_cs5535.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_it821x.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_mpiix.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_ns87410.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_oldpiix.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_radisys.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_sc1200.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_sil680.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ata/pata_via.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/atm/firestream.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/block/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/block/loop.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/block/nbd.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/block/rd.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/cyclades.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_hashtab.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_hashtab.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_mm.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_pci.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_sarea.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_sman.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/drm_sman.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/r128_drv.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/radeon_irq.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/radeon_state.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/sis_mm.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/via_mm.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/drm/via_verifier.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/esp.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/hw_random/omap-rng.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/i8k.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/n_tty.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/rocket.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/sonypi.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/tty_io.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/char/tty_ioctl.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/firewire/fw-transaction.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/hid/usbhid/hid-ff.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/hwmon/gl520sm.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/hwmon/sis5595.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/hwmon/via686a.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/algos/i2c-algo-bit.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/algos/i2c-algo-pca.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/algos/i2c-algo-pcf.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-elektor.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-hydra.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-ibm_iic.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-omap.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-parport.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-via.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/busses/i2c-viapro.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/i2c/i2c-core.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ide/ide-cd.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ide/ide-tape.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ide/legacy/q40ide.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ide/pci/it821x.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/ide/pci/siimage.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/input/fixp-arith.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/input/joystick/db9.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/input/misc/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/input/mouse/psmouse-base.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/input/mouse/vsxxxaa.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/act2000/act2000_isa.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/hisax/amd7930_fn.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/hisax/enternow_pci.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/hisax/hfc_pci.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/hisax/isdnhdlc.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/hisax/isdnhdlc.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/hisax/jade.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/isdn/pcbit/capi.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/leds/leds-s3c24xx.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/macintosh/via-pmu.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/md/dm-crypt.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/md/raid1.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/common/saa7146_hlp.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/dvb/bt8xx/bt878.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/video/meye.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/video/meye.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/video/saa5246a.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/video/saa5249.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/media/video/v4l2-common.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/message/i2o/README
浏览文件 @ c00046c2
此差异已折叠。
drivers/message/i2o/exec-osm.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/message/i2o/i2o_config.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/message/i2o/i2o_proc.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/message/i2o/iop.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/message/i2o/pci.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/mfd/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/misc/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/misc/ibmasm/remote.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/misc/sony-laptop.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/mtd/maps/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/8139too.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/amd8111e.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/ariadne.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/ariadne.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/au1000_eth.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/bonding/bond_sysfs.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/e100.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/e1000/e1000_main.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/fealnx.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/hamradio/6pack.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/hamradio/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/actisys-sir.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/actisys.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/donauboe.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/girbil-sir.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/girbil.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/irport.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/irtty-sir.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/nsc-ircc.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/nsc-ircc.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/tekram-sir.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/tekram.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/irda/w83977af_ir.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/natsemi.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/smc911x.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/spider_net.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/tc35815.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/tulip/winbond-840.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/usb/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/via-velocity.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/wireless/ipw2100.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/wireless/ipw2200.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/net/wireless/netwave_cs.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/rtc/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/s390/block/dasd_3990_erp.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/s390/char/sclp_cpi.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/s390/cio/cmf.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/s390/net/ctcmain.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/aacraid/aacraid.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/aha152x.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/aic7xxx/cam.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/dc395x.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/qla4xxx/ql4_init.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/sd.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/sun3_NCR5380.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/sym53c8xx_2/sym_fw2.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/scsi/wd33c93.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/serial/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/serial/s3c2410.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/spi/mpc52xx_psc_spi.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/gadget/lh7a40x_udc.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/host/ehci-hub.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/host/sl811-hcd.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/image/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/misc/cytherm.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/misc/emi26.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/misc/emi62.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/serial/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/serial/ftdi_sio.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/serial/ftdi_sio.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/serial/ipaq.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/storage/isd200.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/usb/storage/unusual_devs.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/amifb.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/aty/atyfb_base.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/console/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/intelfb/intelfbdrv.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/intelfb/intelfbhw.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/omap/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/s3c2410fb.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/vermilion/vermilion.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/video/vermilion/vermilion.h
浏览文件 @ c00046c2
此差异已折叠。
drivers/watchdog/i6300esb.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/watchdog/w83697hf_wdt.c
浏览文件 @ c00046c2
此差异已折叠。
drivers/zorro/zorro.ids
浏览文件 @ c00046c2
此差异已折叠。
fs/binfmt_em86.c
浏览文件 @ c00046c2
此差异已折叠。
fs/binfmt_misc.c
浏览文件 @ c00046c2
此差异已折叠。
fs/binfmt_script.c
浏览文件 @ c00046c2
此差异已折叠。
fs/isofs/inode.c
浏览文件 @ c00046c2
此差异已折叠。
fs/jfs/jfs_dtree.c
浏览文件 @ c00046c2
此差异已折叠。
fs/nfs/nfsroot.c
浏览文件 @ c00046c2
此差异已折叠。
fs/ntfs/ChangeLog
浏览文件 @ c00046c2
此差异已折叠。
fs/ntfs/sysctl.c
浏览文件 @ c00046c2
此差异已折叠。
fs/ntfs/sysctl.h
浏览文件 @ c00046c2
此差异已折叠。
fs/ocfs2/dcache.c
浏览文件 @ c00046c2
此差异已折叠。
fs/reiserfs/super.c
浏览文件 @ c00046c2
此差异已折叠。
fs/super.c
浏览文件 @ c00046c2
此差异已折叠。
fs/sysfs/file.c
浏览文件 @ c00046c2
此差异已折叠。
include/asm-arm/dma-mapping.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-blackfin/system.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-h8300/system.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-m68knommu/system.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-mips/pci/bridge.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-powerpc/io.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-powerpc/paca.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-sh/se7751.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-sh/systemh7751.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-sh64/system.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-v850/system.h
浏览文件 @ c00046c2
此差异已折叠。
include/asm-x86/hpet.h
浏览文件 @ c00046c2
此差异已折叠。
include/linux/cdrom.h
浏览文件 @ c00046c2
此差异已折叠。
include/linux/crypto.h
浏览文件 @ c00046c2
此差异已折叠。
include/linux/fs.h
浏览文件 @ c00046c2
此差异已折叠。
include/linux/ipmi_smi.h
浏览文件 @ c00046c2
此差异已折叠。
include/linux/security.h
浏览文件 @ c00046c2
此差异已折叠。
include/net/irda/irttp.h
浏览文件 @ c00046c2
此差异已折叠。
init/main.c
浏览文件 @ c00046c2
此差异已折叠。
kernel/hrtimer.c
浏览文件 @ c00046c2
此差异已折叠。
kernel/panic.c
浏览文件 @ c00046c2
此差异已折叠。
kernel/power/snapshot.c
浏览文件 @ c00046c2
此差异已折叠。
kernel/sched.c
浏览文件 @ c00046c2
此差异已折叠。
kernel/taskstats.c
浏览文件 @ c00046c2
此差异已折叠。
lib/argv_split.c
浏览文件 @ c00046c2
此差异已折叠。
lib/kernel_lock.c
浏览文件 @ c00046c2
此差异已折叠。
lib/kobject_uevent.c
浏览文件 @ c00046c2
此差异已折叠。
mm/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
mm/hugetlb.c
浏览文件 @ c00046c2
此差异已折叠。
mm/memory.c
浏览文件 @ c00046c2
此差异已折叠。
mm/memory_hotplug.c
浏览文件 @ c00046c2
此差异已折叠。
mm/mempool.c
浏览文件 @ c00046c2
此差异已折叠。
mm/migrate.c
浏览文件 @ c00046c2
此差异已折叠。
mm/nommu.c
浏览文件 @ c00046c2
此差异已折叠。
mm/page-writeback.c
浏览文件 @ c00046c2
此差异已折叠。
mm/page_alloc.c
浏览文件 @ c00046c2
此差异已折叠。
mm/prio_tree.c
浏览文件 @ c00046c2
此差异已折叠。
mm/slab.c
浏览文件 @ c00046c2
此差异已折叠。
mm/swap.c
浏览文件 @ c00046c2
此差异已折叠。
mm/vmalloc.c
浏览文件 @ c00046c2
此差异已折叠。
mm/vmscan.c
浏览文件 @ c00046c2
此差异已折叠。
net/9p/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
net/ax25/ax25_ds_in.c
浏览文件 @ c00046c2
此差异已折叠。
net/ax25/ax25_ds_subr.c
浏览文件 @ c00046c2
此差异已折叠。
net/bluetooth/bnep/core.c
浏览文件 @ c00046c2
此差异已折叠。
net/bluetooth/bnep/netdev.c
浏览文件 @ c00046c2
此差异已折叠。
net/bridge/netfilter/ebtables.c
浏览文件 @ c00046c2
此差异已折叠。
net/core/pktgen.c
浏览文件 @ c00046c2
此差异已折叠。
net/ieee80211/ieee80211_wx.c
浏览文件 @ c00046c2
此差异已折叠。
net/ipv4/Kconfig
浏览文件 @ c00046c2
此差异已折叠。
net/irda/discovery.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/iriap.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/iriap_event.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irias_object.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_client.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_client_event.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_common.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_eth.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_event.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_filter.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlan/irlan_provider.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlap_event.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlap_frame.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlmp.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlmp_event.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irlmp_frame.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irmod.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irqueue.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irsysctl.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/irttp.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/timer.c
浏览文件 @ c00046c2
此差异已折叠。
net/irda/wrapper.c
浏览文件 @ c00046c2
此差异已折叠。
net/iucv/iucv.c
浏览文件 @ c00046c2
此差异已折叠。
net/netfilter/xt_CONNMARK.c
浏览文件 @ c00046c2
此差异已折叠。
net/netfilter/xt_connmark.c
浏览文件 @ c00046c2
此差异已折叠。
net/netfilter/xt_limit.c
浏览文件 @ c00046c2
此差异已折叠。
net/sched/em_meta.c
浏览文件 @ c00046c2
此差异已折叠。
sound/core/seq/seq_midi_emul.c
浏览文件 @ c00046c2
此差异已折叠。
sound/drivers/opl3/opl3_midi.c
浏览文件 @ c00046c2
此差异已折叠。
sound/isa/es18xx.c
浏览文件 @ c00046c2
此差异已折叠。
sound/mips/au1x00.c
浏览文件 @ c00046c2
此差异已折叠。
sound/pci/au88x0/au88x0.c
浏览文件 @ c00046c2
此差异已折叠。
sound/soc/soc-core.c
浏览文件 @ c00046c2
此差异已折叠。
sound/soc/soc-dapm.c
浏览文件 @ c00046c2
此差异已折叠。
sound/synth/emux/emux_synth.c
浏览文件 @ c00046c2
此差异已折叠。
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或