Eric Lee / linux-smarc-t335x-v3.2

Download as
Browse Code ยป

Commit 3706baa8b1ba0d71d52fd0c656752a6495f6364a

Authored by Alexey Dobriyan
Committed by Linus Torvalds
1 parent eb84a20e9e
Exists in master and in 4 other branches v3.2_AM335xPSP_04.06.00.11, v3.2_NEWT335xPSP_04.06.00.11, v3.2_SBC_SMARTMEN, v3.2_SMARCT335xPSP_04.06.00.11

[PATCH] Documentation/SubmittingDrivers: minor update 

* fix copright typo
* remove trailing whitespace
* remove Kernel Traffic from Resources. Zack, it was great reading!
* Name Arjan by name and fix URL of "How to NOT" paper.
* Remove "Last updated" tag.

Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Showing 1 changed file with 7 additions and 14 deletions Side-by-side Diff

Documentation/SubmittingDrivers
Diff comments   View file @ 3706baa
... ... @@ -59,11 +59,11 @@
59 59 are the same person/entity. If not, the name of
60 60 the person/entity authorizing use of GPL should be
61 61 listed in case it's necessary to verify the will of
62   - the copright owner.
  62 + the copyright owner.
63 63  
64 64 Interfaces: If your driver uses existing interfaces and behaves like
65 65 other drivers in the same class it will be much more likely
66   - to be accepted than if it invents gratuitous new ones.
  66 + to be accepted than if it invents gratuitous new ones.
67 67 If you need to implement a common API over Linux and NT
68 68 drivers do it in userspace.
69 69  
... ... @@ -88,7 +88,7 @@
88 88 it will go in the bitbucket.
89 89  
90 90 Control: In general if there is active maintainance of a driver by
91   - the author then patches will be redirected to them unless
  91 + the author then patches will be redirected to them unless
92 92 they are totally obvious and without need of checking.
93 93 If you want to be the contact and update point for the
94 94 driver it is a good idea to state this in the comments,
... ... @@ -100,7 +100,7 @@
100 100 Vendor: Being the hardware vendor and maintaining the driver is
101 101 often a good thing. If there is a stable working driver from
102 102 other people already in the tree don't expect 'we are the
103   - vendor' to get your driver chosen. Ideally work with the
  103 + vendor' to get your driver chosen. Ideally work with the
104 104 existing driver author to build a single perfect driver.
105 105  
106 106 Author: It doesn't matter if a large Linux company wrote the driver,
107 107  
... ... @@ -116,17 +116,13 @@
116 116 ftp.??.kernel.org:/pub/linux/kernel/...
117 117 ?? == your country code, such as "us", "uk", "fr", etc.
118 118  
119   -Linux kernel mailing list:
  119 +Linux kernel mailing list:
120 120 linux-kernel@vger.kernel.org
121 121 [mail majordomo@vger.kernel.org to subscribe]
122 122  
123 123 Linux Device Drivers, Third Edition (covers 2.6.10):
124 124 http://lwn.net/Kernel/LDD3/ (free version)
125 125  
126   -Kernel traffic:
127   - Weekly summary of kernel list activity (much easier to read)
128   - http://www.kerneltraffic.org/kernel-traffic/
129   -
130 126 LWN.net:
131 127 Weekly summary of kernel development activity - http://lwn.net/
132 128 2.6 API changes:
133 129  
... ... @@ -145,12 +141,9 @@
145 141 Linux USB project:
146 142 http://www.linux-usb.org/
147 143  
148   -How to NOT write kernel driver by arjanv@redhat.com
149   - http://people.redhat.com/arjanv/olspaper.pdf
  144 +How to NOT write kernel driver by Arjan van de Ven:
  145 + http://www.fenrus.org/how-to-not-write-a-device-driver-paper.pdf
150 146  
151 147 Kernel Janitor:
152 148 http://janitor.kernelnewbies.org/
153   -
154   ---
155   -Last updated on 17 Nov 2005.