diff options
| author | Stephen Rothwell <sfr@canb.auug.org.au> | 2008-02-02 22:15:07 +1100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@suse.de> | 2008-02-02 15:14:49 -0800 |
| commit | 44414e14af3f18fc8c1b94e259cd760366f665ee (patch) | |
| tree | b815066b3f124b978d763053b01cf3a779341e62 /Documentation/driver-model/platform.txt | |
| parent | cd35449b93ac128282c1f1f720e84c5935f9018e (diff) | |
Driver core: Update some prototypes in platform.txt
Just make these match the actual code.
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'Documentation/driver-model/platform.txt')
| -rw-r--r-- | Documentation/driver-model/platform.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/driver-model/platform.txt b/Documentation/driver-model/platform.txt index 2a97320ee17f..83009fdcbbc8 100644 --- a/Documentation/driver-model/platform.txt +++ b/Documentation/driver-model/platform.txt @@ -122,15 +122,15 @@ None the less, there are some APIs to support such legacy drivers. Avoid using these calls except with such hotplug-deficient drivers. struct platform_device *platform_device_alloc( - char *name, unsigned id); + const char *name, int id); You can use platform_device_alloc() to dynamically allocate a device, which you will then initialize with resources and platform_device_register(). A better solution is usually: struct platform_device *platform_device_register_simple( - char *name, unsigned id, - struct resource *res, unsigned nres); + const char *name, int id, + struct resource *res, unsigned int nres); You can use platform_device_register_simple() as a one-step call to allocate and register a device. |