diff options
| author | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2019-06-18 12:34:59 -0300 |
|---|---|---|
| committer | Mauro Carvalho Chehab <mchehab+samsung@kernel.org> | 2019-07-15 11:03:02 -0300 |
| commit | fe34c89d25429e079ba67416529514120dd715f8 (patch) | |
| tree | 31a1ab717619c97b8711803d8815a22aa77ce2dd /drivers/staging | |
| parent | 56198359b64125dd0f9fa991972b61e4bc4fc6b5 (diff) | |
| download | lwn-fe34c89d25429e079ba67416529514120dd715f8.tar.gz lwn-fe34c89d25429e079ba67416529514120dd715f8.zip | |
docs: driver-model: move it to the driver-api book
The audience for the Kernel driver-model is clearly Kernel hackers.
Signed-off-by: Mauro Carvalho Chehab <mchehab+samsung@kernel.org>
Acked-by: Jeff Kirsher <jeffrey.t.kirsher@intel.com> # ice driver changes
Diffstat (limited to 'drivers/staging')
| -rw-r--r-- | drivers/staging/unisys/Documentation/overview.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/staging/unisys/Documentation/overview.txt b/drivers/staging/unisys/Documentation/overview.txt index 9ab30af265a5..f8a4144b239c 100644 --- a/drivers/staging/unisys/Documentation/overview.txt +++ b/drivers/staging/unisys/Documentation/overview.txt @@ -15,7 +15,7 @@ normally be unsharable, specifically: * visorinput - keyboard and mouse These drivers conform to the standard Linux bus/device model described -within Documentation/driver-model/, and utilize a driver named visorbus to +within Documentation/driver-api/driver-model/, and utilize a driver named visorbus to present the virtual busses involved. Drivers in the 'visor*' driver set are commonly referred to as "guest drivers" or "client drivers". All drivers except visorbus expose a device of a specific usable class to the Linux guest @@ -141,7 +141,7 @@ called automatically by the visorbus driver at appropriate times: ----------------------------------- Because visorbus is a standard Linux bus driver in the model described in -Documentation/driver-model/, the hierarchy of s-Par virtual devices is +Documentation/driver-api/driver-model/, the hierarchy of s-Par virtual devices is published in the sysfs tree beneath /bus/visorbus/, e.g., /sys/bus/visorbus/devices/ might look like: |