summaryrefslogtreecommitdiffstats
path: root/Documentation/sparc/sbus_drivers.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/sparc/sbus_drivers.txt')
-rw-r--r--Documentation/sparc/sbus_drivers.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/sparc/sbus_drivers.txt b/Documentation/sparc/sbus_drivers.txt
index 4b9351624f13..8418d35484fc 100644
--- a/Documentation/sparc/sbus_drivers.txt
+++ b/Documentation/sparc/sbus_drivers.txt
@@ -25,8 +25,8 @@ the bits necessary to run your device. The most commonly
used members of this structure, and their typical usage,
will be detailed below.
- Here is a piece of skeleton code for perofming a device
-probe in an SBUS driverunder Linux:
+ Here is a piece of skeleton code for performing a device
+probe in an SBUS driver under Linux:
static int __devinit mydevice_probe_one(struct sbus_dev *sdev)
{
@@ -98,7 +98,7 @@ in your .remove method.
Any memory allocated, registers mapped, IRQs registered,
etc. must be undone by your .remove method so that all resources
-of your device are relased by the time it returns.
+of your device are released by the time it returns.
You should _NOT_ use the for_each_sbus(), for_each_sbusdev(),
and for_all_sbusdev() interfaces. They are deprecated, will be
OpenPOWER on IntegriCloud