Commit be7d2f775c788a1891f0f600537f130178448b20
Committed by
Adrian Bunk
1 parent
1b3c3714cb
Exists in
master
and in
7 other branches
trivial documentation patch for platform.txt
Found a couple of typos in the Documentation/driver-model/platform.txt file. This patch fixes both of them. Signed-off-by: Erik Hovland <erik@hovland.org> Signed-off-by: Adrian Bunk <bunk@stusta.de>
Showing 1 changed file with 2 additions and 2 deletions Side-by-side Diff
Documentation/driver-model/platform.txt
... | ... | @@ -66,7 +66,7 @@ |
66 | 66 | |
67 | 67 | Device Enumeration |
68 | 68 | ~~~~~~~~~~~~~~~~~~ |
69 | -As a rule, platform specific (and often board-specific) setup code wil | |
69 | +As a rule, platform specific (and often board-specific) setup code will | |
70 | 70 | register platform devices: |
71 | 71 | |
72 | 72 | int platform_device_register(struct platform_device *pdev); |
... | ... | @@ -106,7 +106,7 @@ |
106 | 106 | * platform_device.id ... the device instance number, or else "-1" |
107 | 107 | to indicate there's only one. |
108 | 108 | |
109 | -These are catenated, so name/id "serial"/0 indicates bus_id "serial.0", and | |
109 | +These are concatenated, so name/id "serial"/0 indicates bus_id "serial.0", and | |
110 | 110 | "serial/3" indicates bus_id "serial.3"; both would use the platform_driver |
111 | 111 | named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id) |
112 | 112 | and use the platform_driver called "my_rtc". |