Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit b160292c authored by David Woodhouse's avatar David Woodhouse
Browse files

Merge Linux 2.6.23

parents b37bde14 bbf25010

Documentation/00-INDEX

+0 −2
Original line number Diff line number Diff line
@@ -134,8 +134,6 @@ dvb/ 
	- info on Linux Digital Video Broadcast (DVB) subsystem.

early-userspace/

	- info about initramfs, klibc, and userspace early during boot.

ecryptfs.txt

	- docs on eCryptfs: stacked cryptographic filesystem for Linux.

eisa.txt

	- info on EISA bus support.

exception.txt

Documentation/DocBook/deviceiobook.tmpl

+2 −1
Original line number Diff line number Diff line
@@ -316,7 +316,8 @@ CPU B: spin_unlock_irqrestore(&dev_lock, flags) 


  <chapter id="pubfunctions">

     <title>Public Functions Provided</title>

!Einclude/asm-i386/io.h

!Iinclude/asm-i386/io.h

!Elib/iomap.c

  </chapter>



</book>

Documentation/HOWTO

+2 −2
Original line number Diff line number Diff line
@@ -208,7 +208,7 @@ tools. One such tool that is particularly recommended is the Linux 
Cross-Reference project, which is able to present source code in a

self-referential, indexed webpage format. An excellent up-to-date

repository of the kernel code may be found at:

	http://sosdg.org/~coywolf/lxr/

	http://users.sosdg.org/~qiyong/lxr/





The development process
@@ -384,7 +384,7 @@ One of the best ways to put into practice your hacking skills is by fixing 
bugs reported by other people. Not only you will help to make the kernel

more stable, you'll learn to fix real world problems and you will improve

your skills, and other developers will be aware of your presence. Fixing

bugs is one of the best ways to earn merit amongst the developers, because

bugs is one of the best ways to get merits among other developers, because

not many people like wasting time fixing other people's bugs.



To work in the already reported bug reports, go to http://bugzilla.kernel.org.

Documentation/ManagementStyle

+1 −1
Original line number Diff line number Diff line
@@ -166,7 +166,7 @@ To solve this problem, you really only have two options: 
The option of being unfailingly polite really doesn't exist. Nobody will

trust somebody who is so clearly hiding his true character.



(*) Paul Simon sang "Fifty Ways to Lose Your Lover", because quite

(*) Paul Simon sang "Fifty Ways to Leave Your Lover", because quite

frankly, "A Million Ways to Tell a Developer He Is a D*ckhead" doesn't

scan nearly as well.  But I'm sure he thought about it.

Documentation/SubmittingPatches

+2 −2
Original line number Diff line number Diff line
@@ -126,7 +126,7 @@ the reviewers time and will get your patch rejected, probably 
without even being read.



At a minimum you should check your patches with the patch style

checker prior to submission (scripts/patchcheck.pl).  You should

checker prior to submission (scripts/checkpatch.pl).  You should

be able to justify all violations that remain in your patch.
@@ -560,7 +560,7 @@ NO!!!! No more huge patch bombs to linux-kernel@vger.kernel.org people! 
  <http://marc.theaimsgroup.com/?l=linux-kernel&m=112112749912944&w=2>



Kernel Documentation/CodingStyle:

  <http://sosdg.org/~coywolf/lxr/source/Documentation/CodingStyle>

  <http://users.sosdg.org/~qiyong/lxr/source/Documentation/CodingStyle>



Linus Torvalds's mail on the canonical patch format:

  <http://lkml.org/lkml/2005/4/7/183>