diff options
author | Matt LaPlante <kernel1@cyberdogtech.com> | 2007-10-20 01:34:40 +0200 |
---|---|---|
committer | Adrian Bunk <bunk@kernel.org> | 2007-10-20 01:34:40 +0200 |
commit | 01dd2fbf0da4019c380b6ca22a074538fb31db5a (patch) | |
tree | 210291bd341c4450c8c51d8db890af0978f4035d /Documentation/driver-model | |
parent | 0f035b8e8491f4ff87f6eec3e3f754d36b39d7a2 (diff) | |
download | kernel_samsung_smdk4412-01dd2fbf0da4019c380b6ca22a074538fb31db5a.zip kernel_samsung_smdk4412-01dd2fbf0da4019c380b6ca22a074538fb31db5a.tar.gz kernel_samsung_smdk4412-01dd2fbf0da4019c380b6ca22a074538fb31db5a.tar.bz2 |
typo fixes
Most of these fixes were already submitted for old kernel versions, and were
approved, but for some reason they never made it into the releases.
Because this is a consolidation of a couple old missed patches, it touches both
Kconfigs and documentation texts.
Signed-off-by: Matt LaPlante <kernel1@cyberdogtech.com>
Acked-by: Randy Dunlap <randy.dunlap@oracle.com>
Signed-off-by: Adrian Bunk <bunk@kernel.org>
Diffstat (limited to 'Documentation/driver-model')
-rw-r--r-- | Documentation/driver-model/devres.txt | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt index 8569072..387b8a7 100644 --- a/Documentation/driver-model/devres.txt +++ b/Documentation/driver-model/devres.txt @@ -32,7 +32,7 @@ braindamaged document, if it's finally working, well, it's working. For one reason or another, low level drivers don't receive as much attention or testing as core code, and bugs on driver detach or -initilaization failure doesn't happen often enough to be noticeable. +initialization failure don't happen often enough to be noticeable. Init failure path is worse because it's much less travelled while needs to handle multiple entry points. @@ -160,7 +160,7 @@ resources on failure. For example, devres_release_group(dev, NULL); return err_code; -As resource acquision failure usually means probe failure, constructs +As resource acquisition failure usually means probe failure, constructs like above are usually useful in midlayer driver (e.g. libata core layer) where interface function shouldn't have side effect on failure. For LLDs, just returning error code suffices in most cases. |