forked from torvalds/linux
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial
* git://git.kernel.org/pub/scm/linux/kernel/git/bunk/trivial: (79 commits) Jesper Juhl is the new trivial patches maintainer Documentation: mention email-clients.txt in SubmittingPatches fs/binfmt_elf.c: spello fix do_invalidatepage() comment typo fix Documentation/filesystems/porting fixes typo fixes in net/core/net_namespace.c typo fix in net/rfkill/rfkill.c typo fixes in net/sctp/sm_statefuns.c lib/: Spelling fixes kernel/: Spelling fixes include/scsi/: Spelling fixes include/linux/: Spelling fixes include/asm-m68knommu/: Spelling fixes include/asm-frv/: Spelling fixes fs/: Spelling fixes drivers/watchdog/: Spelling fixes drivers/video/: Spelling fixes drivers/ssb/: Spelling fixes drivers/serial/: Spelling fixes drivers/scsi/: Spelling fixes ...
- Loading branch information
Showing
255 changed files
with
382 additions
and
442 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -508,12 +508,8 @@ D: REINER SCT cyberJack pinpad/e-com USB chipcard reader driver | |
S: Germany | ||
|
||
N: Adrian Bunk | ||
E: [email protected] | ||
P: 1024D/4F12B400 B29C E71E FE19 6755 5C8A 84D4 99FC EA98 4F12 B400 | ||
D: misc kernel hacking and testing | ||
S: Grasmeierstrasse 11 | ||
S: 80805 Muenchen | ||
S: Germany | ||
|
||
N: Ray Burr | ||
E: [email protected] | ||
|
@@ -1124,6 +1120,9 @@ S: 1150 Ringwood Court | |
S: San Jose, California 95131 | ||
S: USA | ||
|
||
N: Adam Fritzler | ||
E: [email protected] | ||
|
||
N: Fernando Fuganti | ||
E: [email protected] | ||
E: [email protected] | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -53,7 +53,7 @@ Finding it the old way | |
|
||
[Sat Mar 2 10:32:33 PST 1996 KERNEL_BUG-HOWTO [email protected] (Larry McVoy)] | ||
|
||
This is how to track down a bug if you know nothing about kernel hacking. | ||
This is how to track down a bug if you know nothing about kernel hacking. | ||
It's a brute force approach but it works pretty well. | ||
|
||
You need: | ||
|
@@ -66,12 +66,12 @@ You will then do: | |
|
||
. Rebuild a revision that you believe works, install, and verify that. | ||
. Do a binary search over the kernels to figure out which one | ||
introduced the bug. I.e., suppose 1.3.28 didn't have the bug, but | ||
introduced the bug. I.e., suppose 1.3.28 didn't have the bug, but | ||
you know that 1.3.69 does. Pick a kernel in the middle and build | ||
that, like 1.3.50. Build & test; if it works, pick the mid point | ||
between .50 and .69, else the mid point between .28 and .50. | ||
. You'll narrow it down to the kernel that introduced the bug. You | ||
can probably do better than this but it gets tricky. | ||
can probably do better than this but it gets tricky. | ||
|
||
. Narrow it down to a subdirectory | ||
|
||
|
@@ -81,27 +81,27 @@ You will then do: | |
directories: | ||
|
||
Copy the non-working directory next to the working directory | ||
as "dir.63". | ||
as "dir.63". | ||
One directory at time, try moving the working directory to | ||
"dir.62" and mv dir.63 dir"time, try | ||
"dir.62" and mv dir.63 dir"time, try | ||
|
||
mv dir dir.62 | ||
mv dir.63 dir | ||
find dir -name '*.[oa]' -print | xargs rm -f | ||
|
||
And then rebuild and retest. Assuming that all related | ||
changes were contained in the sub directory, this should | ||
isolate the change to a directory. | ||
changes were contained in the sub directory, this should | ||
isolate the change to a directory. | ||
|
||
Problems: changes in header files may have occurred; I've | ||
found in my case that they were self explanatory - you may | ||
found in my case that they were self explanatory - you may | ||
or may not want to give up when that happens. | ||
|
||
. Narrow it down to a file | ||
|
||
- You can apply the same technique to each file in the directory, | ||
hoping that the changes in that file are self contained. | ||
hoping that the changes in that file are self contained. | ||
|
||
. Narrow it down to a routine | ||
|
||
- You can take the old file and the new file and manually create | ||
|
@@ -130,7 +130,7 @@ You will then do: | |
that makes the difference. | ||
|
||
Finally, you take all the info that you have, kernel revisions, bug | ||
description, the extent to which you have narrowed it down, and pass | ||
description, the extent to which you have narrowed it down, and pass | ||
that off to whomever you believe is the maintainer of that section. | ||
A post to linux.dev.kernel isn't such a bad idea if you've done some | ||
work to narrow it down. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3177,7 +3177,7 @@ S: Maintained | |
|
||
RAYLINK/WEBGEAR 802.11 WIRELESS LAN DRIVER | ||
P: Corey Thomas | ||
M: [email protected] | ||
M: [email protected] | ||
L: [email protected] | ||
S: Maintained | ||
|
||
|
@@ -3790,18 +3790,9 @@ L: [email protected] | |
S: Maintained | ||
|
||
TRIVIAL PATCHES | ||
P: Adrian Bunk | ||
P: Jesper Juhl | ||
M: [email protected] | ||
L: [email protected] | ||
W: http://www.kernel.org/pub/linux/kernel/people/bunk/trivial/ | ||
T: git kernel.org:/pub/scm/linux/kernel/git/bunk/trivial.git | ||
S: Maintained | ||
|
||
TMS380 TOKEN-RING NETWORK DRIVER | ||
P: Adam Fritzler | ||
M: [email protected] | ||
L: [email protected] | ||
W: http://www.auk.cx/tms380tr/ | ||
S: Maintained | ||
|
||
TULIP NETWORK DRIVER | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.