From 8e83013c743e57ebceec437bd54b0e6cb1cd0864 Mon Sep 17 00:00:00 2001 From: Erik Hovland Date: Thu, 6 Oct 2005 10:47:49 -0700 Subject: [PATCH] --- yaml --- r: 10539 b: refs/heads/master c: 2a7ff1feda9f5cd6463744239ec5e661ee7d5f01 h: refs/heads/master i: 10537: e1045beed43691fd43ec2bf50ab562a9d15f0d91 10535: 74acb50df6cfcb84dbe7b9a0fac16deb33e4f17f v: v3 --- [refs] | 2 +- trunk/Documentation/driver-model/porting.txt | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/[refs] b/[refs] index 0adaa84e2288..471d21cf2522 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 4ed17dccd69c4fc13b9d2118001f5e58ea16ebea +refs/heads/master: 2a7ff1feda9f5cd6463744239ec5e661ee7d5f01 diff --git a/trunk/Documentation/driver-model/porting.txt b/trunk/Documentation/driver-model/porting.txt index ff2fef2107f0..98b233cb8b36 100644 --- a/trunk/Documentation/driver-model/porting.txt +++ b/trunk/Documentation/driver-model/porting.txt @@ -350,7 +350,7 @@ When a driver is registered, the bus's list of devices is iterated over. bus->match() is called for each device that is not already claimed by a driver. -When a device is successfully bound to a device, device->driver is +When a device is successfully bound to a driver, device->driver is set, the device is added to a per-driver list of devices, and a symlink is created in the driver's sysfs directory that points to the device's physical directory: