diff options
author | Erik Hovland <erik@hovland.org> | 2007-02-17 19:29:21 +0100 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2007-02-17 19:29:21 +0100 |
commit | be7d2f775c788a1891f0f600537f130178448b20 (patch) | |
tree | d0558ca15f3707781b8ae6f30a4c59e73b8f35ed | |
parent | 1b3c3714cb4767d00f507cc6854d3339d82c5b9d (diff) |
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>
-rw-r--r-- | Documentation/driver-model/platform.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/driver-model/platform.txt b/Documentation/driver-model/platform.txt index 9f0bc3bfd77..f7c9262b2dc 100644 --- a/Documentation/driver-model/platform.txt +++ b/Documentation/driver-model/platform.txt @@ -66,7 +66,7 @@ runtime memory footprint: Device Enumeration ~~~~~~~~~~~~~~~~~~ -As a rule, platform specific (and often board-specific) setup code wil +As a rule, platform specific (and often board-specific) setup code will register platform devices: int platform_device_register(struct platform_device *pdev); @@ -106,7 +106,7 @@ It's built from two components: * platform_device.id ... the device instance number, or else "-1" to indicate there's only one. -These are catenated, so name/id "serial"/0 indicates bus_id "serial.0", and +These are concatenated, so name/id "serial"/0 indicates bus_id "serial.0", and "serial/3" indicates bus_id "serial.3"; both would use the platform_driver named "serial". While "my_rtc"/-1 would be bus_id "my_rtc" (no instance id) and use the platform_driver called "my_rtc". |