This is a note to let you know that I've just added the patch titled
Subject: Driver core: Update some prototypes in platform.txt
to my gregkh-2.6 tree. Its filename is
driver-core-update-some-prototypes-in-platform.txt.patch
This tree can be found at
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/patches/
>From [EMAIL PROTECTED] Sat Feb 2 12:50:36 2008
From: Stephen Rothwell <[EMAIL PROTECTED]>
Date: Sat, 2 Feb 2008 22:15:07 +1100
Subject: Driver core: Update some prototypes in platform.txt
To: Greg Kroah-Hartman <[EMAIL PROTECTED]>
Cc: LKML <linux-kernel@vger.kernel.org>
Message-ID: <[EMAIL PROTECTED]>
Just make these match the actual code.
Signed-off-by: Stephen Rothwell <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
Documentation/driver-model/platform.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--- a/Documentation/driver-model/platform.txt
+++ b/Documentation/driver-model/platform.txt
@@ -122,15 +122,15 @@ None the less, there are some APIs to su
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.
Patches currently in gregkh-2.6 which might be from [EMAIL PROTECTED] are
bad/battery-class-driver.patch
driver/ppc-fix-powerpc-vio_find_name-to-not-use-devices_subsys.patch
driver/driver-core-update-some-prototypes-in-platform.txt.patch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
