From 96a2fcff895411b4edeea408f8e798062d5feded Mon Sep 17 00:00:00 2001 From: R Veera Kumar Date: Thu, 19 Mar 2020 14:27:57 +0530 Subject: [PATCH] staging: unisys: Documentation: Correct a long line in doc Correct a long line in documentation to respect the 80 character line limit. Found using checkpatch.pl. Signed-off-by: R Veera Kumar Link: https://lore.kernel.org/r/20200319085751.GA1928@tulip.local Signed-off-by: Greg Kroah-Hartman --- drivers/staging/unisys/Documentation/overview.txt | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/unisys/Documentation/overview.txt b/drivers/staging/unisys/Documentation/overview.txt index f8a4144b239c5..cf29f884cbe04 100644 --- a/drivers/staging/unisys/Documentation/overview.txt +++ b/drivers/staging/unisys/Documentation/overview.txt @@ -15,12 +15,12 @@ normally be unsharable, specifically: * visorinput - keyboard and mouse These drivers conform to the standard Linux bus/device model described -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 -environment (e.g., block, network, or input), and are collectively referred -to as "function drivers". +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 environment (e.g., block, network, or input), and are collectively +referred to as "function drivers". The back-end for each device is owned and managed by a small, single-purpose service partition in the s-Par firmware, which communicates -- 2.30.2