diff options
| author | Steven Cole <elenstev@mesatop.com> | 2005-05-03 21:07:24 -0400 |
|---|---|---|
| committer | Greg KH <gregkh@suse.de> | 2005-05-04 02:31:52 -0400 |
| commit | 093cf723b2b06d774929ea07982f6a466ff22314 (patch) | |
| tree | 9199ddc8a4ed6dfdc427134333f99b97245e6408 /drivers/usb/input | |
| parent | 7b1cbebaa7ced7a2029cc5b50eab60c79b24cc10 (diff) | |
[PATCH] USB: Spelling fixes for drivers/usb.
Here are some spelling corrections for drivers/usb.
cancelation -> cancellation
succesful -> successful
cancelation -> cancellation
decriptor -> descriptor
Initalize -> Initialize
wierd -> weird
Protocoll -> Protocol
occured -> occurred
successfull -> successful
Procesing -> Processing
devide -> divide
Isochronuous -> Isochronous
noticable -> noticeable
Basicly -> Basically
transfering -> transferring
intialize -> initialize
Incomming -> Incoming
additionnal -> additional
asume -> assume
Unfortunatly -> Unfortunately
retreive -> retrieve
tranceiver -> transceiver
Compatiblity -> Compatibility
Incorprated -> Incorporated
existance -> existence
Ununsual -> Unusual
Signed-off-by: Steven Cole <elenstev@mesatop.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/usb/input')
| -rw-r--r-- | drivers/usb/input/aiptek.c | 2 | ||||
| -rw-r--r-- | drivers/usb/input/mtouchusb.c | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/drivers/usb/input/aiptek.c b/drivers/usb/input/aiptek.c index 2d76be62f4e0..94ce2a9ad50f 100644 --- a/drivers/usb/input/aiptek.c +++ b/drivers/usb/input/aiptek.c | |||
| @@ -386,7 +386,7 @@ static int aiptek_convert_from_2s_complement(unsigned char c) | |||
| 386 | * convention above.) I therefore have taken over REL_MISC and ABS_MISC | 386 | * convention above.) I therefore have taken over REL_MISC and ABS_MISC |
| 387 | * (for relative and absolute reports, respectively) for communicating | 387 | * (for relative and absolute reports, respectively) for communicating |
| 388 | * Proximity. Why two events? I thought it interesting to know if the | 388 | * Proximity. Why two events? I thought it interesting to know if the |
| 389 | * Proximity event occured while the tablet was in absolute or relative | 389 | * Proximity event occurred while the tablet was in absolute or relative |
| 390 | * mode. | 390 | * mode. |
| 391 | * | 391 | * |
| 392 | * Other tablets use the notion of a certain minimum stylus pressure | 392 | * Other tablets use the notion of a certain minimum stylus pressure |
diff --git a/drivers/usb/input/mtouchusb.c b/drivers/usb/input/mtouchusb.c index 6b45a66d58c1..ab1a2a30ce7c 100644 --- a/drivers/usb/input/mtouchusb.c +++ b/drivers/usb/input/mtouchusb.c | |||
| @@ -32,7 +32,7 @@ | |||
| 32 | * Changed reset from standard USB dev reset to vendor reset | 32 | * Changed reset from standard USB dev reset to vendor reset |
| 33 | * Changed data sent to host from compensated to raw coordinates | 33 | * Changed data sent to host from compensated to raw coordinates |
| 34 | * Eliminated vendor/product module params | 34 | * Eliminated vendor/product module params |
| 35 | * Performed multiple successfull tests with an EXII-5010UC | 35 | * Performed multiple successful tests with an EXII-5010UC |
| 36 | * | 36 | * |
| 37 | * 1.5 02/27/2005 ddstreet@ieee.org | 37 | * 1.5 02/27/2005 ddstreet@ieee.org |
| 38 | * Added module parameter to select raw or hw-calibrated coordinate reporting | 38 | * Added module parameter to select raw or hw-calibrated coordinate reporting |