From f94e5b6bb83cd55b542cfc95cac4a55a4ab6250c Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Sat, 28 May 2011 19:11:39 -0400 Subject: [PATCH] --- yaml --- r: 259184 b: refs/heads/master c: b6badddcccf9d48a01e9a9b33c47922976291ab6 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/Documentation/driver-model/device.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 7e472e74e2c4..bec3ebcf5be4 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 5464e9c72194d4db9665346b3973c1fb27ba87be +refs/heads/master: b6badddcccf9d48a01e9a9b33c47922976291ab6 diff --git a/trunk/Documentation/driver-model/device.txt b/trunk/Documentation/driver-model/device.txt index b2ff42685bcb..bdefe728a737 100644 --- a/trunk/Documentation/driver-model/device.txt +++ b/trunk/Documentation/driver-model/device.txt @@ -104,4 +104,4 @@ Then in the module init function is would do: And assuming 'dev' is the struct device passed into the probe hook, the driver probe function would do something like: - create_device(&mydriver_class, dev, chrdev, &private_data, "my_name"); + device_create(&mydriver_class, dev, chrdev, &private_data, "my_name");